CVE-2025-47514
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 Eli ELI's Related Posts Footer Links and Widget spostarbust allows Stored XSS.This issue affects ELI's Related Posts Footer Links and Widget: from n/a through <= 1.2.04.20.
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 ELI's Related Posts Footer Links and Widget plugin (spostarbust) allows attackers to craft malicious requests that, when triggered by an authenticated administrator, inject persistent cross-site scripting (Stored XSS) into the plugin's output. This affects versions up to 1.2.04.20, enabling script execution for all users viewing 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.
-
Confirm plugin installationCheck your WordPress plugins directory (wp-content/plugins) for a folder named 'spostarbust' or 'related-posts-footer-links-and-widget' or containing 'eli' related posts functionalityAffected if The plugin folder is not found in the plugins directory, you are not affected
-
Identify installed versionOpen the main plugin PHP file (usually index.php or the primary plugin file in the spostarbust folder) and locate the 'Version' header in the plugin comment block; compare this version number to 1.2.04.20Affected if The installed version is 1.2.04.20 or any earlier version (e.g., 1.2.04.19, 1.2.04.10), you are affected
-
Verify plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and check if 'ELI's Related Posts Footer Links and Widget' or 'Related Posts Footer Links and Widget' is activatedAffected if The plugin is activated, the CSRF attack surface exists; if deactivated, you are not currently vulnerable
-
Check for plugin output on frontendView the source HTML of your site pages (especially blog posts or articles) and search for 'spostarbust', 'related-posts-footer', or the plugin's widget output being renderedAffected if The plugin output appears on your pages, the stored XSS can be injected and will execute for all visitors viewing that content
If the plugin is installed, active, version 1.2.04.20 or below, and its output is displayed on your site, your environment is affected by this CVE and the stored XSS can be triggered via CSRF against an authenticated administrator.
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 dataUpdate to the latest plugin version once available; alternatively, disable the plugin until a patch is released. Implement CSRF token validation for all admin-side actions and ensure proper output sanitization.
- 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-47514 — 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-47514 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