{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 2.3.6"
      },
      "package": {
        "ecosystem": "Packagist",
        "name": "froxlor/froxlor"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.3.7"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [],
  "database_specific": {
    "cwe_ids": [
      "CWE-200"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-07-02T19:23:31Z",
    "nvd_published_at": null,
    "severity": "MODERATE"
  },
  "details": "## Summary\n\nAn authenticated customer can read other customers\u0027 allowed sender aliases from Froxlor\u0027s sender-delete confirmation page when `mail.enable_allow_sender` is enabled. `customer_email.php` loads `allowed_sender` by global auto-increment `senderid` alone, so a customer can enumerate foreign sender alias IDs and make Froxlor disclose those values in the confirmation dialog for the attacker\u0027s own mailbox.\n\n## Details\n\nThe vulnerable read lives in `customer_email.php`:\n\n```php\n$senderid = Request::any(\u0027senderid\u0027, 0);\n...\n$sel_stmt = Database::prepare(\"SELECT `allowed_sender` FROM `\" . TABLE_MAIL_SENDER_ALIAS . \"` WHERE `id` = :sid\");\n$sender_data = Database::pexecute_first($sel_stmt, [\u0027sid\u0027 =\u003e $senderid]);\n\nHTML::askYesNo(\u0027email_reallydelete_sender\u0027, $filename, [\n    \u0027id\u0027 =\u003e $id,\n    \u0027senderid\u0027 =\u003e $senderid,\n    \u0027page\u0027 =\u003e $page,\n    \u0027domainid\u0027 =\u003e $email_domainid,\n    \u0027action\u0027 =\u003e $action\n], $idna_convert-\u003edecode($result[\u0027email_full\u0027]) . \u0027 -\u003e \u0027 . $sender_data[\u0027allowed_sender\u0027]);\n```\n\nThe query does not scope `senderid` to the current customer or to the mailbox being edited. `mail_sender_aliases.id` is a global `AUTO_INCREMENT` primary key:\n\n```sql\nCREATE TABLE `mail_sender_aliases` (\n  `id` int(11) NOT NULL auto_increment,\n  `email` varchar(255) NOT NULL,\n  `allowed_sender` varchar(255) NOT NULL,\n  PRIMARY KEY  (`id`)\n)\n```\n\nThat makes sender alias IDs enumerable. A customer who owns any mailbox with sender-alias management enabled can request the delete-confirmation page for their own mailbox while supplying foreign `senderid` values. Froxlor then renders the foreign `allowed_sender` string in the confirmation prompt.\n\n## Proof of Concept\n\nVerified against Froxlor `2.3.6` on a fresh test install with `mail.enable_allow_sender=1`.\n\n1. Create two customers, `victim` and `attacker`.\n2. Give each customer one mailbox.\n3. Add a sender alias for the victim mailbox:\n\n```text\ninfo@victim.local -\u003e leaked-sender@example.org\n```\n\n4. Log in as the attacker and request the delete-confirmation page for the attacker\u0027s own mailbox while supplying the victim\u0027s sender alias ID:\n\n```text\n/customer_email.php?page=senders\u0026domainid=4\u0026action=delete\u0026id=2\u0026senderid=1\n```\n\nObserved in the live test instance:\n\n```text\nDo you really want to delete the allowed sender info@attacker.local -\u003e leaked-sender@example.org?\n```\n\nThe attacker-controlled mailbox identifier stayed `info@attacker.local`, but the disclosed sender alias text came from the victim-owned row identified by `senderid=1`.\n\n## Impact\n\nAn authenticated customer can enumerate global sender alias IDs and read other customers\u0027 allowed sender values. This is a cross-tenant information disclosure. It does not let the attacker delete the foreign alias because the delete action revalidates ownership.\n\n## Recommended Fix\n\nScope the sender alias lookup to the current customer and mailbox before rendering the confirmation page. The confirmation flow should fetch the sender alias through the same ownership checks used by `EmailSender::delete()`.\n\n---\n*Found by [aisafe.io](https://aisafe.io)*",
  "id": "GHSA-mr9h-45p9-fg8h",
  "modified": "2026-07-02T19:23:31Z",
  "published": "2026-07-02T19:23:31Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/froxlor/froxlor/security/advisories/GHSA-mr9h-45p9-fg8h"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/froxlor/froxlor"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Froxlor: Authenticated customers can read other customers\u0027 allowed sender aliases"
}