MEDIUM 6.4

CVE-2026-8494: Stored XSS in Permalink Manager Lite WordPress Plugin

Permalink Manager Lite, a WordPress plugin, contains a security flaw in its admin interface that allows contributors and higher-level users to embed malicious scripts into post titles. When an administrator later visits the Permalink Manager page, that script executes in their browser. The vulnerability exists in all versions up to 2.5.3.3 and requires an authenticated attacker with at least contributor privileges to exploit.

Source data · NVD / CISA · public domain

CVSS
3.1 · 6.4 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Weaknesses (CWE)
CWE-79
Affected products
0 configuration(s)
Published / Modified
2026-06-17 / 2026-06-17

NVD description (verbatim)

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.

5 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-8494 is a Stored Cross-Site Scripting (XSS) vulnerability in the Permalink Manager Lite WordPress plugin affecting versions ≤2.5.3.3. The flaw stems from insufficient output escaping of post titles within the admin URI Editor interface. An authenticated attacker with Contributor-level or higher permissions can inject arbitrary JavaScript payloads via the post title field. Because the malicious payload is stored server-side and rendered without proper sanitization whenever an administrator accesses the Permalink Manager page, the injected script executes in the admin's session—potentially allowing session hijacking, credential theft, or further WordPress infrastructure compromise.

Business impact

This vulnerability poses a meaningful risk to WordPress sites that rely on the Permalink Manager Lite plugin and permit contributor-level access. In collaborative editorial environments, a compromised or malicious contributor can inject persistent scripts that target administrators, potentially leading to privilege escalation, unauthorized administrative actions, or lateral movement within the WordPress ecosystem. Affected organizations face operational disruption, data exposure, and reputational damage if an attacker gains administrative access through this vector.

Affected systems

Permalink Manager Lite plugin for WordPress in all versions up to and including 2.5.3.3. The vulnerability requires an authenticated user account with Contributor-level permissions or above; this includes Contributors, Editors, Administrators, and any custom roles with equivalent capabilities. Sites that do not use this plugin or that have upgraded beyond version 2.5.3.3 are unaffected.

Exploitability

The vulnerability is moderately exploitable. It requires authentication and contributor-level privileges—meaning an attacker cannot exploit it anonymously or from an unauthenticated state. However, contributor access is often broadly granted in collaborative WordPress sites, and the attack requires no user interaction from the victim (the administrator simply needs to view the affected page for the payload to trigger). No known public exploit code was released as of the CVE publication date.

Remediation

Site administrators should upgrade the Permalink Manager Lite plugin to a patched version above 2.5.3.3. Verify the latest version against the official WordPress plugin repository or the plugin vendor's advisory. As an interim protective measure, restrict Contributor-level permissions to trusted users only, monitor access logs for suspicious activity in the Permalink Manager interface, and consider disabling the plugin if it is not actively used until a patch is deployed.

Patch guidance

Check the official Permalink Manager Lite WordPress plugin repository for an available security update. Upgrade to the earliest patched version following 2.5.3.3. Test the update in a staging environment first to ensure compatibility with your site's configuration, active themes, and other plugins. After deploying to production, verify that post titles and permalinks are rendered correctly across both public and admin pages. Keep the plugin updated regularly to receive future security patches promptly.

Detection guidance

Review administrator access logs and audit trails for the Permalink Manager page to identify when and by whom the page was accessed. Inspect post titles in your WordPress database or via the post editor interface for suspicious HTML or JavaScript tags (e.g., <script>, onclick, onerror). Use WordPress security plugins with XSS detection capabilities to scan stored post content. Monitor browser console errors in the admin dashboard for unexpected script execution. Check commit history or file integrity tools if available to detect unauthorized modifications to post metadata.

Why prioritize this

Although this vulnerability carries a CVSS score of 6.4 (Medium), it warrants timely remediation because it affects a leveraged admin interface, can be exploited by a broad class of authenticated users, and may enable privilege escalation. Organizations with contributor-heavy WordPress installations or sites handling sensitive editorial workflows should treat this as a near-term priority. However, it is lower-priority than critical or high-severity vulnerabilities affecting unauthenticated attack vectors.

Risk score, explained

The CVSS 3.1 score of 6.4 (Medium) reflects a network-accessible vulnerability (AV:N) with low attack complexity (AC:L) that requires authentication and low privilege (PR:L) but imposes no user interaction requirement (UI:N). The impact scope is changed (S:C), affecting the confidentiality and integrity of admin and user data (C:L/I:L), with no availability impact (A:N). The Medium severity balances the practical need for prior authentication against the stored nature of the XSS and its potential for administrative session compromise.

Frequently asked questions

Can an unauthenticated attacker exploit this vulnerability?

No. The vulnerability requires authentication with at least Contributor-level access to WordPress. Unauthenticated users cannot inject the payload.

Does the attacker need to interact with the administrator to trigger the exploit?

No. The malicious script is stored in the database and automatically executes whenever an administrator visits the Permalink Manager page. No phishing or social engineering is required.

What should I do if I use Permalink Manager Lite?

Immediately check for a patched version above 2.5.3.3 on the official WordPress plugin repository and upgrade. If a patch is not yet available, restrict Contributor permissions to trusted users and monitor admin access logs for suspicious activity.

Are other Permalink Manager plugins affected?

This CVE specifically identifies the Permalink Manager Lite plugin. Other permalink management solutions may have different codebases and vulnerabilities. Check each plugin's security advisories separately.

This analysis is provided for informational purposes and reflects publicly disclosed vulnerability data as of the publication date. Security landscape and vendor remediation timelines may evolve; always verify patch availability and compatibility against official vendor advisories before deployment. SEC.co makes no warranty regarding exploit likelihood, real-world impact, or patch applicability to specific environments. Organizations should conduct their own risk assessment and testing in accordance with their security policies and incident response procedures. Source: NVD (public-domain), retrieved 2026-07-27. Analysis generated by SEC.co (claude-haiku-4-5).