CVE-2026-57682
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 Simple Link Directory <= 15.0.5 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 · moderate confidenceAn unauthenticated Cross Site Scripting (XSS) vulnerability exists in the Simple Link Directory WordPress plugin versions 15.0.5 and below. The vulnerability allows attackers to inject malicious JavaScript code through unsanitized user inputs, potentially compromising other users' sessions or performing actions on their behalf.
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 Simple Link Directory plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Simple Link Directory' in the plugin list.Affected if The plugin is present and active in the WordPress installation
-
Check the installed plugin versionIn the plugins list, click on 'Simple Link Directory' or view the plugin details to see the version number. Alternatively, inspect the plugin main file header in wp-content/plugins/simple-link-directory/Affected if The version number is 15.0.5 or lower
-
Identify user input entry pointsExamine the plugin files for forms, search fields, or URL parameters that accept user data. Look for files handling link submissions, directory searches, or front-end listings.Affected if The plugin processes and displays user-supplied data without sanitization
-
Inspect the submission handlerReview PHP files in the plugin directory that process link submissions or search queries. Look for functions that render user input back to the page without escaping.Affected if User input is output to the page without proper sanitization functions such as esc_html(), esc_attr(), or esc_url()
You are affected if Simple Link Directory plugin version 15.0.5 or below is installed and processes user input that is rendered without output escaping.
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 Simple Link Directory to a version newer than 15.0.5. If no update is available, implement output escaping and input validation on all user-supplied data before rendering, or disable the plugin until a patch is released.
Simple Link Directory 15.0.6 or latest available version
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate Simple Link Directory in the plugin list
- Check if the current version is 15.0.5 or lower
- If vulnerable, click 'Update Now' on the Simple Link Directory plugin to install the latest version
- After update, verify the plugin version is higher than 15.0.5
- Clear any site caches if applicable
- Test the plugin functionality to ensure the update did not break existing features
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation3.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57682 — 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-57682 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