CVE-2025-39418
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 ajayver RSS Manager rss-manager allows Stored XSS.This issue affects RSS Manager: from n/a through <= 0.06.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the ajayver RSS Manager plugin (versions <= 0.06) allows authenticated attackers to inject malicious JavaScript code through forged requests, resulting in Stored XSS. The lack of CSRF token validation on state-changing operations enables attackers to trick administrators into unknowingly executing malicious requests that store XSS payloads within the RSS feed data.
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 the ajayver RSS Manager plugin is installedNavigate to WordPress admin > Plugins > Installed Plugins and look for 'ajayver RSS Manager' in the listAffected if Plugin is present and active in the WordPress installation
-
Identify the installed plugin versionIn the plugins list, click on the plugin name or view the plugin files to locate the version number in the plugin header comment (usually in the main PHP file)Affected if Version is 0.06 or lower (any version up to and including 0.06)
-
Verify the plugin has state-changing functionalityAccess the plugin settings page (usually under Settings or a dedicated menu item for RSS Manager) and confirm the ability to add, edit, or save RSS feed dataAffected if Plugin functionality that modifies feed data is accessible and operational
-
Inspect forms for CSRF protectionView the page source of the plugin's admin forms (add/edit feed forms) and search for 'nonce', 'csrf', or 'token' in the form HTML and form handling codeAffected if No anti-CSRF token (nonce) is present in forms that modify feed data, or tokens are not validated on submission
You are affected if the ajayver RSS Manager plugin is installed at version 0.06 or lower and its forms for modifying RSS feed data lack CSRF token validation.
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 anti-CSRF tokens (synchronizer tokens) on all forms and state-changing requests, combined with proper input validation and output encoding to prevent XSS execution.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-39418 — 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-39418 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