CVE-2026-57345
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 · uneditedUnauthenticated Cross Site Scripting (XSS) in Internal Links Manager <= 3.0.3 versions.
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 confidenceUnauthenticated Cross-Site Scripting (XSS) vulnerability in the Internal Links Manager WordPress plugin versions 3.0.3 and below allows remote attackers to inject malicious JavaScript through unsanitized input in internal link handling functions.
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.
-
Verify Internal Links Manager plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Internal Links Manager' in the listAffected if The plugin appears in the installed plugins list regardless of activation status
-
Check installed plugin versionClick on the plugin name in the WordPress plugins list or view the plugin's main PHP file header (usually in wp-content/plugins/internal-links-manager/) to read the 'Version' commentAffected if The reported version is 3.0.3 or any version lower (e.g., 3.0.2, 3.0.1, 3.0.0)
-
Confirm plugin is activeIn WordPress admin > Plugins, verify the plugin has an 'Active' status under the Internal Links Manager entryAffected if The plugin is activated - the XSS is reachable without authentication when the plugin is active
-
Inspect internal link handling functionalityIf the plugin provides a shortcode or frontend interface for internal links (check plugin settings or documentation), attempt to identify where user-supplied input is processed for link parametersAffected if The plugin accepts URL parameters or user input for internal link generation without visible sanitization - however, version comparison in step 2 is the primary indicator of exposure
You are affected if Internal Links Manager plugin is installed and active with version 3.0.3 or lower.
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 Internal Links Manager plugin to version greater than 3.0.3; alternatively, disable or remove the plugin until a patch is available.
Upgrade to Internal Links Manager version 3.0.4 or later
- 1. Backup your WordPress site and database before making any changes
- 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- 3. Locate Internal Links Manager in the plugin list
- 4. Check the current version number to confirm it is 3.0.3 or earlier
- 5. If an update is available, click 'Update Now' to upgrade to the latest version
- 6. If no update appears, manually download the latest version from the official WordPress plugin repository or the plugin vendor website
- 7. Deactivate the current plugin version, then delete it, and install the fresh updated version
- 8. Verify the update was successful by checking the plugin version number after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57345 — 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-2026-57345 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