ghsa-qv78-c8hc-438r
Vulnerability from github
Published
2025-11-03 20:24
Modified
2025-11-06 23:13
Summary
OpenMage vulnerable to XSS in Admin Notifications
Details

Summary

OpenMage versions v20.15.0 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by an admin with direct database access or the admin notification feed source to inject malicious scripts into vulnerable fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field.

Details

Unescaped translation strings and URLs are printed into contexts inside app/code/core/Mage/Adminhtml/Block/Notification/Grid/Renderer/Actions.php. A malicious translation or polluted data can inject script. - Link labels use __() without escaping. - ’deleteConfirm()’ embeds a message without escaping.

PoC

  1. Add XSS to admin locale (e.g. app/locale/en_US/local.csv): "Read Details","<img src=x onerror=alert(123)>" "Mark as Read","<script>alert(123)</script>"
  2. Flush Cache. Make sure locale is set to en_US.
  3. Add any admin notification (e.g. via test.php) <?php require 'app/Mage.php'; Mage::app('admin'); Mage::getModel('adminnotification/inbox')->setData([ 'severity' => Mage_AdminNotification_Model_Inbox::SEVERITY_NOTICE, 'date_added' => now(), 'title' => 'XSS renderer test', 'description' => 'Testing actions renderer', 'url' => 'https://example.com', // makes the "Read Details" link appear 'is_read' => 0, // makes the "Mark as Read" link appear 'is_remove' => 0, ])->save();
  4. Open Admin → System → Notifications → Inbox.
  5. Profit.

Impact

The vulnerability is only exploitable by an attacker with administrative or translation privileges. Malicious JavaScript may be executed in a victim’s browser when they browse to the admin page containing the vulnerable fields.

Show details on source website


{
  "affected": [
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "openmage/magento-lts"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "20.16.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-64174"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-79"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-11-03T20:24:10Z",
    "nvd_published_at": "2025-11-06T21:15:43Z",
    "severity": "MODERATE"
  },
  "details": "### Summary\nOpenMage versions v20.15.0 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by an admin with direct database access or the admin notification feed source to inject malicious scripts into vulnerable fields. Malicious JavaScript may be executed in a victim\u2019s browser when they browse to the page containing the vulnerable field.\n\n### Details\nUnescaped translation strings and URLs are printed into contexts inside `app/code/core/Mage/Adminhtml/Block/Notification/Grid/Renderer/Actions.php`. A malicious translation or polluted data can inject script. \n- Link labels use __() without escaping.\n- \u2019deleteConfirm()\u2019 embeds a message without escaping.\n\n### PoC\n1. Add XSS to admin locale (e.g. app/locale/en_US/local.csv):\n    ```\n    \"Read Details\",\"\u003cimg src=x onerror=alert(123)\u003e\"\n    \"Mark as Read\",\"\u003cscript\u003ealert(123)\u003c/script\u003e\"\n    ```\n2. Flush Cache. Make sure locale is set to en_US.\n3. Add any admin notification (e.g. via test.php)\n     ```\n    \u003c?php\n    require \u0027app/Mage.php\u0027;\n    Mage::app(\u0027admin\u0027);\n    Mage::getModel(\u0027adminnotification/inbox\u0027)-\u003esetData([\n        \u0027severity\u0027  =\u003e Mage_AdminNotification_Model_Inbox::SEVERITY_NOTICE,\n        \u0027date_added\u0027 =\u003e now(),\n        \u0027title\u0027 =\u003e \u0027XSS renderer test\u0027,\n        \u0027description\u0027 =\u003e \u0027Testing actions renderer\u0027,\n        \u0027url\u0027 =\u003e \u0027https://example.com\u0027, // makes the \"Read Details\" link appear\n        \u0027is_read\u0027 =\u003e 0, // makes the \"Mark as Read\" link appear\n        \u0027is_remove\u0027 =\u003e 0,\n    ])-\u003esave();\n    ```\n4. Open Admin \u2192 System \u2192 Notifications \u2192 Inbox.\n5. Profit.\n\n### Impact\nThe vulnerability is only exploitable by an attacker with administrative or translation privileges. Malicious JavaScript may be executed in a victim\u2019s browser when they browse to the admin page containing the vulnerable fields.",
  "id": "GHSA-qv78-c8hc-438r",
  "modified": "2025-11-06T23:13:18Z",
  "published": "2025-11-03T20:24:10Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/OpenMage/magento-lts/security/advisories/GHSA-qv78-c8hc-438r"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-64174"
    },
    {
      "type": "WEB",
      "url": "https://github.com/OpenMage/magento-lts/commit/9d604f5489851c54a96fca31b0e13c414b0fb20a"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/OpenMage/magento-lts"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "OpenMage vulnerable to XSS in Admin Notifications"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…