CVE-2023-0075: Amazon JS <= 0.10 - Contributor+ Stored XSS
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- No fix version is held. The CNA's first reference is the place to look: wpscan.com
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
The Amazon JS WordPress plugin through 0.10 does not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks.
- weakness
- CWE-79 Cross-Site Scripting (XSS)
- affected
- Unknown Amazon JS
- published ranges
- amazonjs project amazonjs <= 0.10
- fixed in
- No fix version in held sources.
- assigned by
- WPScan
- published
- 2023-02-13
check us wpscan.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 14 Feb 2023 | 0.00885 | |
| 7 Mar 2023 | 0.00045 | scoring model v2023.03.01 |
| 8 Mar 2023 | 0.00045 | |
| 14 Jan 2024 | 0.00051 | |
| 17 Mar 2025 | 0.00251 | scoring model v2025.03.14 |
| 21 Nov 2025 | 0.00465 | |
| 10 Dec 2025 | 0.00469 | |
| 14 Feb 2026 | 0.0047 | |
| 15 Jun 2026 | 0.00635 | scoring model v2026.06.15 |
21 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.01 on 2026-06-15 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- No fix version is held. One published by the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2023-0075', '2026-10-29T23:59:59.999999Z', now());