CVE-2025-53331
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 samcharrington RSS Digest rss-digest allows Stored XSS.This issue affects RSS Digest: from n/a through <= 1.5.
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 confidenceA Cross-Site Request Forgery (CSRF) vulnerability in the RSS Digest plugin (versions up to 1.5) allows attackers to trick authenticated users into submitting malicious requests that result in Stored XSS. The attacker can inject malicious scripts through RSS feed content that gets stored and executed when other users view the feed.
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.
-
Identify if RSS Digest plugin is installedLocate the plugin directory or use the CMS/plugin management interface to list installed plugins. Look for a plugin named 'RSS Digest' or similar.Affected if The RSS Digest plugin is present in the installation.
-
Check the installed version of RSS Digest pluginAccess the plugin details page in the CMS admin panel or inspect the plugin's main file header for the version string.Affected if The version is 1.5 or lower (the vulnerability affects versions up to 1.5).
-
Verify the RSS feed functionality is accessibleCheck if the RSS feed generation endpoint or feature is enabled and publicly or internally accessible. Look for routes like /feed, /rss, or a custom RSS Digest endpoint.Affected if The RSS feed feature is enabled and users can view stored feed content.
-
Confirm authenticated user access to the pluginReview user role permissions and determine if authenticated users have the ability to add or modify RSS feed sources through the plugin interface.Affected if Authenticated users can interact with the plugin to add or modify RSS feed content.
-
Inspect for anti-CSRF protections in plugin requestsExamine the plugin's forms or API calls for the presence of anti-CSRF tokens (such as nonces). Check the HTML source of plugin admin pages for nonce fields.Affected if Anti-CSRF tokens are missing from state-changing operations in the plugin.
You are affected if the RSS Digest plugin version 1.5 or lower is installed, the RSS feed feature is enabled, and the plugin lacks anti-CSRF protections on its state-changing operations.
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 for all state-changing operations and add proper input validation and output encoding for RSS feed content to prevent stored XSS.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53331 — 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-53331 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