Custom Simple RssWordPress extension · Custom Simple Rss Project
CVE-2019-14327
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 · uneditedA CSRF vulnerability in Settings form in the Custom Simple Rss plugin 2.0.6 for WordPress allows attackers to change the plugin settings.
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 confidenceA CSRF (Cross-Site Request Forgery) vulnerability exists in the Custom Simple RSS WordPress plugin version 2.0.6. The plugin's settings form lacks proper anti-CSRF token (nonce) verification, allowing authenticated administrators to unknowingly submit malicious form requests when tricked by attackers into visiting crafted 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
Custom Simple RssWordPress extension
<= 2.0.6CVSS 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
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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.
-
Verify plugin installation and versionNavigate to WordPress admin dashboard > Plugins > Installed Plugins and locate 'Custom Simple Rss' in the list. Check the version number displayed below the plugin name.Affected if The plugin is installed and the version is 2.0.6 or lower.
-
Locate the plugin settings fileAccess the WordPress site via FTP or file manager and navigate to wp-content/plugins/custom-simple-rss/. Identify the main plugin PHP file that handles settings form submission (typically the main plugin file or a file containing form processing logic).Affected if The plugin file exists in the plugins directory.
-
Inspect settings form for nonce fieldOpen the plugin's settings PHP file and locate the HTML form that handles plugin settings. Search for 'wp_nonce_field' or '_wpnonce' within the form markup.Affected if The form HTML does not contain wp_nonce_field() or a hidden nonce field, indicating missing CSRF protection.
-
Check form processing for nonce validationIn the same settings PHP file, locate the code that processes form submissions (typically in an if/else block checking for POST requests). Search for 'check_admin_referer', 'wp_verify_nonce', or 'wp_nonce_verify' before any settings are saved.Affected if The form processing code lacks nonce verification functions, meaning any authenticated admin can unknowingly submit settings changes.
The environment is affected if Custom Simple RSS plugin version 2.0.6 or lower is installed and the settings form code does not implement nonce verification.
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 dataImplement WordPress nonce verification on the settings form by adding wp_nonce_field() to the form and validating the nonce with check_admin_referer() or wp_verify_nonce() before processing any settings changes.
Fix this in Custom Simple Rss
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14327 — 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-14327 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