CVSS 3.1
7.2 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:NCVE-2026-12424 ARforms <= 7.2.4 - Unauthenticated Stored Cross-Site Scripting via Referer Header
High (7.2). EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
The ARforms plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Referer Header in all versions up to, and including, 7.2.4 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The arf_save_incomplete_form_data() AJAX handler is registered with wp_ajax_nopriv_, meaning unauthenticated attackers can store a malicious payload by submitting a partial form entry with a forged Referer header, with no authentication required at any step.
Severity
- EPSS
- 0.3% estimated probability of exploitation activity in the next 30 days; 22nd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-79 Improper Neutralization of Input During Web Page Generation (Cross-site Scripting)
- OWASP Top 10
- A05:2025 Injection
- Published
- Modified
- Assigned by
- Wordfence (CNA)
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-12424 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-12424?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-12424?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-12424 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-12424)
HTML:
<a href="https://cve.bz/cve/CVE-2026-12424"><img src="https://cve.bz/cve/badge/CVE-2026-12424.svg" alt="CVE-2026-12424"></a>
Attack patterns (CAPEC)
- CAPEC-63 Cross-Site Scripting (XSS) Likelihood: High · Severity: Very High
- CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
- CAPEC-209 XSS Using MIME Type Mismatch Severity: Medium
- CAPEC-588 DOM-Based XSS Likelihood: High · Severity: Very High
- CAPEC-591 Reflected XSS Likelihood: High · Severity: Very High
- CAPEC-592 Stored XSS Likelihood: High · Severity: Very High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.
History
- The NVD deferred its analysis
Changes since this site first stored the record. The same for every record: /api/public/changes.