CformsiiWordPress extension · Cformsii Project
CVE-2014-10377
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 · uneditedThe cforms2 plugin before 13.2 for WordPress has XSS in lib_ajax.php.
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 · moderate confidenceThe cforms2 WordPress plugin before version 13.2 contains a Cross-Site Scripting (XSS) vulnerability in the lib_ajax.php file. The vulnerability allows attackers to inject malicious scripts through unsanitized input processed by this file, potentially compromising other users or administrators viewing affected pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
CformsiiWordPress extension
< 13.2CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify cforms2 plugin versionNavigate to WordPress admin > Plugins > Installed Plugins and locate the cforms2 plugin entry to view its current version number, or check the plugin's main PHP file header for the Version fieldAffected if The installed version is displayed as lower than 13.2 (for example, 13.1, 13.0, or earlier)
-
Locate lib_ajax.php fileAccess the WordPress wp-content/plugins/cforms directory via file manager or FTP, and verify the presence of the lib_ajax.php fileAffected if The file exists at wp-content/plugins/cforms/lib_ajax.php and the plugin version is below 13.2
-
Confirm plugin is activeCheck the WordPress admin Plugins page to determine whether the cforms2 plugin is currently activated on the siteAffected if The plugin shows as Active and the version is below 13.2
-
Verify AJAX endpoint accessibilityAttempt to access the AJAX endpoint URL pattern such as /wp-content/plugins/cforms/lib_ajax.php?ajaxid=somevalue via curl or browser request to confirm the file processes user inputAffected if The endpoint responds and processes parameters without sanitization (version below 13.2 must be confirmed first)
You are affected if the cforms2 plugin is installed, active, and its version is lower than 13.2, as this combination means the vulnerable lib_ajax.php file is in use.
Generated from the published advisory. Verify against your own configuration.
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 data13.2
Update the cforms2 plugin to version 13.2 or later. If immediate updating is not feasible, consider disabling the plugin or implementing Web Application Firewall (WAF) rules to filter malicious requests to the affected endpoint.
Fix this in Cformsii
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2014-10377 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-10377 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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