Skip to main content

Premmerce Permalink Manager CVE-2026-97272

| EUVDEUVD-2026-89922 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-09-30 Patchstack GHSA-2qf2-r4c3-79j9
7.1
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft malicious XSS payload in plugin input
  2. Delivery
    Deliver link to logged-in WordPress user
  3. Exploit
    Victim loads page, script executes in wp-admin
  4. Execution
    Hijack session or forge admin actions
  5. Impact
    Escalate to site compromise

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an unauthenticated attacker to deliver a crafted payload through the Premmerce Permalink Manager for WooCommerce plugin (<= 2.3.13) AND a victim (typically a logged-in administrator) to view the attacker-influenced content - the UI:R metric confirms this required user interaction is the primary limiting factor. It further requires the target WordPress site to run WooCommerce with this specific plugin installed and active. The scope change (S:C) indicates the injected script executes in a different security context (the browser/admin session) than the vulnerable plugin. No authentication is needed by the attacker (PR:N), but the dependency on victim interaction and the specific plugin/WooCommerce deployment meaningfully narrows realistic exploitation.

Impact

The CVSS 3.1 score of 7.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L) reflects a network-reachable, low-complexity, unauthenticated reflected/stored XSS whose severity is inflated by the scope-change (S:C) flag and the aggregation of three low impacts rather than by any high-impact outcome. The single most important limiting signal is UI:R - successful exploitation requires an administrator or other victim to load attacker-influenced content, so this is not a wormable or self-propagating flaw. No EPSS score, no CISA KEV listing, and no public proof-of-concept were provided, so there is no evidence of active exploitation; exploitation status is 'no public exploit identified at time of analysis.' The description is sparse: it does not specify the injectable parameter, the sink, or whether the XSS is reflected or stored, which materially affects real-world weaponizability (stored XSS against wp-admin would be more dangerous than a reflected variant needing social engineering). Net: a genuine but moderate, patch-and-move-on issue rather than an emergency - real priority is bounded by the required user interaction, the confidentiality/integrity impacts being only Low, and the plugin's limited deployment footprint.

Exploit ScenarioDerived

An unauthenticated attacker crafts a URL or submits input to a vulnerable Premmerce Permalink Manager endpoint that reflects or stores unsanitized data, then lures a logged-in WordPress administrator to view it. When the victim's browser renders the page, attacker JavaScript executes in the wp-admin origin, enabling session/cookie theft, admin-action forgery, or injection of persistent backdoors. No public PoC is currently identified, and the attack depends on victim interaction (UI:R).

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 30, 2026

Unauthenticated cross-site scripting in Premmerce Permalink Manager for WooCommerce (versions 2.3.13 and earlier) allows remote attackers to inject script that executes in the context of a victim's browser when the crafted content is rendered. Because the CVSS vector carries PR:N with UI:R, no attacker credentials are required, but successful exploitation depends on a victim - typically a logged-in WordPress administrator - interacting with the attacker-influenced page, which is the primary limiting factor; the S:C scope-change flag means the injected script runs in a different security context (the admin session/browser) than the vulnerable plugin itself. No public exploit code or confirmed active exploitation was identified at time of analysis, and the site must be running WooCommerce with this specific plugin installed and active for exposure.

RemediationAI

No vendor-released patch version is specified in the available intelligence; the advisory at https://patchstack.com/database/wordpress/plugin/woo-permalink-manager/vulnerability/wordpress-premmerce-permalink-manager-for-woocommerce-plugin-2-3-13-cross-site-scripting-xss-vulnerability should be checked for the currently fixed release, and any published update above 2.3.13 should be applied as the primary fix. If an updated build is not yet available or cannot be deployed, the most effective compensating control is to deactivate and, if possible, uninstall the Premmerce Permalink Manager for WooCommerce plugin - the trade-off is loss of its permalink/URL customization functionality and any storefront URL structures that depend on it, so this should be staged against a backup or maintenance window. Where the plugin must remain live, restrict wp-admin and WooCommerce administrative pages to trusted networks or a VPN and enforce least-privilege roles so fewer high-value admin sessions are exposed to a malicious page, noting this limits lateral reach but does not remove the injection itself. A WAF or reverse-proxy rule set targeting reflected/stored script payloads in the plugin's request paths can filter known patterns, though signature-based filtering is bypassable and may block legitimate admin input if tuned too aggressively. Deploying a restrictive Content-Security-Policy that disallows inline and third-party script on admin pages reduces payload execution, but requires careful policy tuning and testing to avoid breaking WordPress admin and WooCommerce functionality, and encouraging administrators to avoid following untrusted links or visiting arbitrary pages while authenticated lowers the chance the UI:R interaction prerequisite is ever satisfied.

Affected VersionsENISA

Premmerce Permalink Manager for WooCommerce n/a ≤2.3.13

Affected Packages

euvd premmerce_permalink_manager_for_woocommerce no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The issue is a CWE-79 improper neutralization of input during web page generation (cross-site scripting) affecting the WordPress plugin Premmerce Permalink Manager for WooCommerce, a permalink/URL customization extension for WooCommerce stores. CPE data confirms the affected component as the plugin package across all 2.3.x builds up to and including 2.3.13 (cpe:2.3:a:premmerce:premmerce_permalink_manager_for_woocommerce:*:*:*:*:*:*:*:*), meaning any resolved version at or below that build inherits the flaw. Per the independent assessment, the vulnerable code fails to sanitize or escape attacker-controlled input before reflecting or storing it into a page, allowing a payload to be delivered over the network (AV:N) with low complexity (AC:L) and no attacker authentication (PR:N). The scope-change metric (S:C) reflects that script execution crosses from the plugin/page context into the victim's browser session, and the C:L/I:L/A:L triad indicates limited - not full - confidentiality, integrity, and availability impact, consistent with cookie/session disclosure, page defacement, or redirect-style outcomes rather than server compromise. The UI:R metric confirms a required victim view of the crafted output, so this is best characterized as an interaction-dependent XSS rather than a self-executing remote compromise.

Know when Premmerce Permalink Manager For Woocommerce gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 7.1 HIGH
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
vuln.today AI 7.1 HIGH

Network-reachable unauthenticated XSS (AV:N/PR:N) needing victim interaction (UI:R); browser-context execution crosses scope (S:C) with limited C/I/A impact typical of XSS.

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:L/SI:L/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

DescriptionCVE.org

Unauthenticated Cross Site Scripting (XSS) in Premmerce Permalink Manager for WooCommerce <= 2.3.13 versions.

Executive ViewAI

Why It Matters

Premmerce Permalink Manager for WooCommerce (versions 2.3.13 and earlier) contains an unauthenticated cross-site scripting vulnerability that could let an attacker execute malicious scripts in a logged-in WordPress administrator's browser, potentially leading to full site takeover, data theft, or unauthorized transactions. E-commerce organizations running WooCommerce with this plugin are affected, and while exploitation requires administrator interaction and no public exploit was identified at time of analysis, the lack of a vendor patch raises the risk. Leadership should prioritize identifying exposed sites and implementing interim safeguards to protect administrative sessions and customer data.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include disabling the plugin if not required, restricting administrative access to trusted networks, enforcing multi-factor authentication, deploying WAF rules to filter XSS payloads, and monitoring for vendor updates. Apply vendor patch when released.

Threat Intelligence Overview

EPSS Score
0.3%
Top 85% exploitable
Prevalence
Low
niche WooCommerce permalink plugin, limited install base
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy