CVE-2025-25139
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Cynob IT Consultancy WP Custom Post RSS Feed wp-custom-post-rss-feed allows Stored XSS.This issue affects WP Custom Post RSS Feed: from n/a through <= 1.0.0.
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 vulnerability in the WP Custom Post RSS Feed WordPress plugin enables attackers to inject malicious scripts via Stored XSS. The lack of proper nonce validation in plugin forms or AJAX actions allows authenticated administrators to be tricked into submitting crafted requests that store malicious JavaScript in the database, which then executes when viewed by other users.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'WP Custom Post RSS Feed' in the list of active pluginsAffected if the plugin appears in the active plugins list
-
Identify plugin versionClick on the plugin name in the plugins list to view version details, or inspect the plugin header in wp-content/plugins/wp-custom-post-rss-feed/plugin-name.phpAffected if version information is unavailable or cannot be compared to a fixed release
-
Inspect plugin forms for nonce validationExamine plugin PHP files for wp_nonce_field in form definitions and wp_verify_nonce or check_admin_referer in form handling codeAffected if plugin forms or AJAX actions lack nonce verification logic (wp_nonce_field, wp_verify_nonce, or check_admin_referer calls)
-
Inspect output escaping on stored dataSearch plugin PHP files for esc_html, esc_attr, esc_url, or wp_kses functions when outputting any data that could be stored in the databaseAffected if stored plugin data is echoed without proper escaping functions, allowing unsanitized content to render in pages
-
Check database for suspicious stored contentUse phpMyAdmin or WP-CLI to query postmeta or custom tables where the plugin stores feed configuration, looking for script tags or javascript: URIs in text fieldsAffected if database contains unexpected script tags, iframe elements, or event handlers in plugin-related fields
If the WP Custom Post RSS Feed plugin is active and its forms/AJAX handlers lack nonce validation, the environment is vulnerable to stored XSS via CSRF.
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 nonces (wp_nonce_field/wp_verify_nonce) on all form submissions and AJAX hooks, and apply proper output escaping (esc_html, esc_attr, wp_kses) to prevent stored XSS.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-25139 — 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-2025-25139 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