Contact Form to Any API Stored XSS in CF7 form submissions
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The Contact Form to Any API plugin for WordPress has a stored cross-site scripting flaw that lets an unauthenticated attacker remotely inject malicious scripts into pages, which then run for any user who opens an affected page. The attacker needs only a single request, with no login or user interaction required.
Written by a model
Original description
The Contact Form to Any API plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'your-message (any CF7 form field)' parameter in all versions up to, and including, 3.0.7 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 malicious payload is stored via a single unauthenticated POST to Contact Form 7's public REST feedback endpoint, which uses permission_callback __return_true and requires no authentication or prior interaction to submit.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-131822 (Contact Form to Any API <= 3.0.7 - Unauthenticated Stored Cross-Site Scripting via CF7 Form Field Submissions), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-131822 (entry last updated 2026-11-21):
Affected:
- itpathsolutions Contact Form to Any API: through 3.0.7
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131822 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131822 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/3c0753da-2807-46d1-b002-d557e7f3bf13?source=cve
- https://plugins.trac.wordpress.org/browser/contact-form-to-any-api/tags/3.0.7/admin/partials/cf7-to-any-api-admin-entries.php#L115
- https://plugins.trac.wordpress.org/browser/contact-form-to-any-api/tags/3.0.7/admin/class-cf7-to-any-api-admin.php#L759
- https://plugins.trac.wordpress.org/browser/contact-form-to-any-api/tags/3.0.7/admin/class-cf7-to-any-api-admin.php#L640
- https://plugins.trac.wordpress.org/browser/contact-form-to-any-api/tags/3.0.7/includes/class-cf7-to-any-api.php#L181
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3811674%40contact-form-to-any-api&new=3811674%40contact-form-to-any-api
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-131822
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131822"}.Affected versions
- itpathsolutions Contact Form to Any APIthrough 3.0.7
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.2/10CVSS 7.2
- No patch5/5No patch listed yet
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 8
Questions about CVE-2026-131822
Is CVE-2026-131822 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-131822?
Contact Form to Any API: through 3.0.7.
Source: cve.now feed data
Related
- CVE-2024-7617Contact Form to Any API <= 1.2.4 - Unauthenticated Stored Cross-Site Scripting via Contact Form
- CVE-2026-15735Contact Form to Any API <= 3.0.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'cf7anyapi_form_field' Post Meta
- CVE-2026-1899Any Post Slider <= 1.0.4 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'post_type' Shortcode Attribute
- CVE-2026-134262Admidio 5.0.0 before 5.0.18 Stored XSS via Role Name in Profile View
- CVE-2026-134250Grav Form Plugin 1.1.0 before 9.1.40 Stored XSS via Unsanitized File Uploads
- CVE-2026-124216Orphans <= 3.4.5 - Unauthenticated Stored Cross-Site Scripting via Comment Content
No corrections so far. Something wrong on this page? Report an error.