CVE-2025-57918
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 ERA404 LinkedInclude linkedinclude allows Stored XSS.This issue affects LinkedInclude: from n/a through <= 3.0.4.
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 confidenceCSRF vulnerability in ERA404 LinkedInclude plugin allows attackers to trick authenticated administrators into submitting malicious requests that inject and persist malicious scripts (Stored XSS) into the application. The lack of anti-CSRF tokens on state-changing operations enables this attack chain.
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 ERA404 LinkedInclude plugin is installedLocate plugin files in the CMS plugin directory (typically /wp-content/plugins/ for WordPress or similar path for other CMS). Look for a folder named 'linkedinclude' or 'era404-linkedinclude'.Affected if The plugin folder exists in the system plugins directory.
-
Verify if the plugin is enabledCheck the CMS admin panel under Plugins > Installed Plugins, or inspect the database configuration table that stores plugin active status.Affected if The plugin shows as active or enabled in the CMS.
-
Determine the installed plugin versionOpen the main plugin PHP file (usually index.php or linkedinclude.php) and locate the version comment or header comment which typically contains 'Version: x.x.x'.Affected if The version number is lower than the latest patched version, or if no version is displayed, the plugin lacks version tracking.
-
Inspect state-changing admin actions for CSRF protectionReview the plugin's PHP source code for form submissions and admin actions. Search for 'admin_post', 'init', or action hooks that handle saves/updates. Check if each uses wp_nonce_field(), verify_nonce(), or similar CSRF token functions.Affected if State-changing operations (save, update, delete, import) lack CSRF token validation code.
-
Check for stored XSS vulnerabilities in input handlingExamine the plugin code for functions that save user input to the database (insert, update queries). Verify that input is sanitized using functions like esc_html(), esc_attr(), or sanitize_text_field() before database storage.Affected if User-supplied data is stored without sanitization, or output is rendered without escaping.
A user is affected if the ERA404 LinkedInclude plugin is installed, enabled, and lacks anti-CSRF tokens on its administrative state-changing functions, allowing Stored XSS injection via CSRF attacks.
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 on all state-changing endpoints and validate/sanitize all user-supplied input before storage and rendering. Update to the latest version if available and apply CSP headers to mitigate XSS impact.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-57918 — 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-57918 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