Stored XSS via unsanitized campaign names
Published Apr 14, 2020 · Updated Aug 4, 2024
Stored XSS in Octech Oempro 4.7 through 4.11 allows remote authenticated users to run JavaScript via a crafted campaign name. Campaign.Create accepts CampaignName markup and stores it without neutralizing HTML before the value is rendered. A user must view the stored name, allowing script execution in that user's browser context and limited data access or modification.
Summary
What happened
Stored XSS in Octech Oempro 4.7 through 4.11 allows remote authenticated users to run JavaScript via a crafted campaign name. Campaign.Create accepts CampaignName markup and stores it without neutralizing HTML before the value is rendered. A user must view the stored name, allowing script execution in that user's browser context and limited data access or modification.
The record
- CVE
- CVE-2020-9460
- Published
- Apr 14, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 14, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
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
- CVE-2020-9460 CampaignName XSS payloadproof 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