dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-39449

HIGH · 7.1 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unauthenticated Cross Site Scripting (XSS) in Contact Form to Any API <= 3.0.3 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Unauthenticated Cross Site Scripting (XSS) vulnerability in the Contact Form to Any API WordPress plugin allows remote attackers to inject malicious scripts through form inputs in versions 3.0.3 and below. The lack of authentication requirement means any visitor can exploit this to steal session cookies, perform actions as other users, or deliver malware.

MitigationUpdate Contact Form to Any API to the latest version (greater than 3.0.3) which should contain proper input sanitization. If immediate update is not possible, implement WAF rules to filter XSS payloads in form submission parameters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Contact Form to Any API plugin is installed
    Navigate to WordPress admin dashboard > Plugins page, or inspect the wp-content/plugins/ directory for a folder named 'contact-form-to-any-api' or similar.
    Affected if The plugin folder exists in the WordPress plugins directory.
  2. Identify the installed plugin version
    In WordPress admin, view the plugin details page to see the version number, or check the plugin's main PHP file or readme.txt for the 'Version' header.
    Affected if The installed version is 3.0.3 or any version lower than 3.0.3.
  3. Verify if the plugin is active
    In WordPress admin > Plugins > Installed Plugins, check if Contact Form to Any API shows as 'Active'.
    Affected if The plugin is activated and running on the site.
  4. Check if form submission functionality is in use
    Look for published pages or posts containing forms created by the plugin, or check the plugin's settings for configured forms.
    Affected if The plugin has any active forms accepting user submissions.

The environment is affected if the Contact Form to Any API plugin is installed, active, running version 3.0.3 or below, and has form functionality enabled to accept submissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Contact Form to Any API to the latest version (greater than 3.0.3) which should contain proper input sanitization. If immediate update is not possible, implement WAF rules to filter XSS payloads in form submission parameters.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39449 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-39449 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data