CVE-2025-58859
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 David Merinas Add to Feedly add-to-feedly allows Stored XSS.This issue affects Add to Feedly: from n/a through <= 1.2.11.
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 Add to Feedly WordPress plugin (versions <= 1.2.11) allows authenticated administrators to be tricked into submitting malicious requests that inject stored XSS payloads into the plugin, potentially affecting all users who view the injected content.
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 Add to Feedly plugin is installedAccess your WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Add to Feedly' in the list of active plugins.Affected if The plugin appears in the installed plugins list and is activated.
-
Check installed plugin versionIn the Plugins list, click on the plugin name or view details to find the version number displayed. Compare this to the affected range of versions <= 1.2.11.Affected if The displayed version number is 1.2.11 or lower.
-
Verify if admin forms lack CSRF protectionInspect the plugin PHP files in /wp-content/plugins/add-to-feedly/ (or similar path). Look for admin form handlers and check if they verify nonces using functions like wp_verify_nonce or check_admin_referer.Affected if State-changing admin actions (such as saving plugin settings) do not validate CSRF tokens.
-
Inspect plugin settings for suspicious stored contentNavigate to the plugin settings page in WordPress admin. Check all input fields for unexpected JavaScript tags, event handlers, or encoded payloads that could indicate XSS injection.Affected if The plugin settings database entries or displayed options contain unsanitized script tags or HTML event attributes.
Your environment is affected if the Add to Feedly plugin is installed with version 1.2.11 or lower, and the plugin lacks CSRF nonce validation on its admin forms or contains stored XSS in its settings.
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.
dbcve · scopedUpdate to a patched version of the plugin; if unavailable, disable the plugin until a fix is released. Implementing anti-CSRF tokens (nonces) on all state-changing forms and actions, plus proper output sanitization, is required.
1.2.12 or latest available version
- 1. Log in to your WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Find the 'Add to Feedly' plugin
- 4. Check if an update is available. If so, update to the latest version (likely 1.2.12 or higher)
- 5. If no update is available through the WordPress admin, download the latest version from the official WordPress plugin repository or contact the plugin developer
- 6. After updating, verify the plugin is functioning correctly on your site
Generated from the published advisory — verify against the referenced sources before acting.
- 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-58859 — 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-58859 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