Custom Field SuiteWordPress extension · Custom Field Suite Project
CVE-2019-11871
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 Custom Field Suite plugin before 2.5.15 for WordPress has XSS for editors or admins.
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 confidenceCross-site scripting (XSS) vulnerability in the Custom Field Suite WordPress plugin affecting versions prior to 2.5.15. The flaw allows authenticated users with editor or administrator privileges to inject malicious JavaScript code through custom field inputs, which could then execute in the browsers of other admin users viewing the crafted content.
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
Custom Field SuiteWordPress extension
< 2.5.15CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/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.
-
Locate installed Custom Field Suite versionIn WordPress admin, go to Plugins > Installed Plugins > Custom Field Suite and read the version number from the plugin description. Alternatively, open wp-content/plugins/custom-field-suite/custom-field-suite.php and find the 'Version:' header in the plugin comment block.Affected if Version is displayed as anything less than 2.5.15 (e.g., 2.5.14, 2.5.10, 2.0.0)
-
Verify the exact version numberCompare the installed version string to the affected range. Note that version numbers like 2.5.14, 2.5.13, 2.5.10, 2.4.0, and any version below 2.5.15 are all vulnerable.Affected if The version number is below 2.5.15 (the version number is less than 2.5.15 when compared numerically)
-
Confirm custom field groups existIn WordPress admin, navigate to Custom Field Suite > Field Groups. Check if any field groups are created and active.Affected if One or more custom field groups are defined and active in the plugin
Your environment is affected if the Custom Field Suite plugin version is below 2.5.15 AND you have custom field groups configured.
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 data2.5.15
Update the Custom Field Suite plugin to version 2.5.15 or later to patch the XSS vulnerability. As this is an authenticated attack vector, ensure admin accounts use strong credentials and consider limiting user permissions to the minimum required.
Fix this in Custom Field Suite
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-2019-11871 — 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-2019-11871 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