Stored XSS via unsanitized blog content fields
Published Nov 29, 2022 · Updated Apr 25, 2025
Stored XSS in Amasty Blog Pro for Magento 2 before 2.10.5 allows attackers to run script in an administrator's browser. The posts/preview and posts/save handlers render JavaScript supplied through the short_content or full_content field without neutralizing it. An attacker must submit crafted blog-post content and induce an administrator to preview or save it, exposing data and actions available in that browser session.
Summary
What happened
Stored XSS in Amasty Blog Pro for Magento 2 before 2.10.5 allows attackers to run script in an administrator's browser. The posts/preview and posts/save handlers render JavaScript supplied through the short_content or full_content field without neutralizing it. An attacker must submit crafted blog-post content and induce an administrator to preview or save it, exposing data and actions available in that browser session.
The record
- CVE
- CVE-2022-36433
- Published
- Nov 29, 2022
- Updated
- Apr 25, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 29, 2022CVE publishedPublication date reported by the CVE source.
- Apr 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- afine-com CVE-2022-36433 proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo