Stored script execution via unsanitized checkout surname
Published Jan 26, 2022 · Updated Aug 2, 2024
Stored XSS in Microweber before 1.2.11 allows remote attackers to execute script in a victim's browser through a checkout last name. Checkout routes accepted the untrusted surname without the XSS middleware added by the patch, allowing the value to remain executable. Exploitation requires a checkout submission and a later click on Continue; execution is limited to data and actions available to the victim's browser session.
Summary
What happened
Stored XSS in Microweber before 1.2.11 allows remote attackers to execute script in a victim's browser through a checkout last name. Checkout routes accepted the untrusted surname without the XSS middleware added by the patch, allowing the value to remain executable. Exploitation requires a checkout submission and a later click on Continue; execution is limited to data and actions available to the victim's browser session.
The record
- CVE
- CVE-2022-0379
- Published
- Jan 26, 2022
- Updated
- Aug 2, 2024
- Vendor
- Microweber
- Product
- Microweber
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 26, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <1.2.11
What conditions does exploitation require?
What is affected?
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
- Huntr checkout last-name exploit reportproof 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