dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-8494

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The Permalink Manager Lite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via post titles in the admin URI Editor interface in all versions up to, and including, 2.5.3.3 due to insufficient output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in the admin Permalink Manager page that will execute whenever an administrator accesses the Permalink Manager page.

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 confidence

The Permalink Manager Lite WordPress plugin fails to properly escape output when displaying post titles in its admin URI Editor interface. An authenticated attacker with Contributor-level access can inject malicious JavaScript into post titles that will execute when administrators view the Permalink Manager page, enabling session hijacking and privileged actions.

MitigationUpgrade to version 2.5.3.4 or later which includes proper output escaping. Until then, restrict contributor-level access and sanitize existing post titles containing script tags.

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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Permalink Manager Lite is installed
    Navigate to WordPress admin > Plugins and confirm 'Permalink Manager Lite' is active, or check the plugins directory for 'permalink-manager' folder
    Affected if The plugin is not installed or not present in the environment
  2. Check installed plugin version
    In Plugins list, find Permalink Manager Lite and note the version number displayed; compare against 2.5.3.4
    Affected if Version is lower than 2.5.3.4 (vulnerable versions)
  3. Confirm Contributor-level or higher users exist
    Go to Users > All Users and review the Role column for any users with Contributor, Author, Editor, or Administrator roles
    Affected if At least one user with Contributor-level access or higher exists in WordPress
  4. Verify URI Editor interface is accessible
    Navigate to Permalink Manager > URI Editor in the admin sidebar and confirm the page loads successfully
    Affected if The URI Editor interface loads without access restrictions
  5. Inspect post titles for potential script injection
    In the URI Editor, examine the post title column for titles containing <script> tags, event handlers (onclick, onerror, etc.), or javascript: URIs; alternatively query the wp_posts table for posts with post_type in ('post','page','custom') and post_title containing '<script' or 'javascript:'
    Affected if Any post titles contain raw HTML, script tags, or JavaScript event handlers that would execute when viewed

The environment is affected if Permalink Manager Lite version is below 2.5.3.4, Contributor-level users exist, the URI Editor is accessible, and post titles contain unescaped HTML or script content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 2.5.3.4 or later which includes proper output escaping. Until then, restrict contributor-level access and sanitize existing post titles containing script tags.

Recommended fix Moderate confidence

Permalink Manager Lite version 2.5.3.4 or later

  1. 1. Log in to the WordPress admin dashboard with administrator privileges.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate 'Permalink Manager Lite' in the plugin list.
  4. 4. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org/plugins/permalink-manager/ and upload it via Plugins > Add New > Upload Plugin.
  5. 5. After updating, verify the plugin version is newer than 2.5.3.3.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8494 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8494 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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