Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSubmit crafted content unauthenticated
-
DeliveryStored via unescaped HTML-parser attribute re-emission
-
ExploitAdmin or user views affected page
-
ExecutionScript executes in victim browser
-
ImpactSession/admin-context actions in WordPress
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 that a NON-DEFAULT image delivery mode be enabled in WebP Express (the description ties the flaw to this configuration); on default installs the vulnerable code path is not reached. The flaw is that the plugin's bundled HTML parser re-emits submitted values into element attributes without escaping, so an attacker-controlled value breaks out of the attribute context. Submission does not require authentication (PR:N). The payload is stored and only fires when a user - potentially an administrator - subsequently views the affected page (UI:R), so a viewing victim is a mandatory limiting condition. Limiting factors: non-default configuration must be active, a victim must load the page, and CVSS marks AC:H (conditions beyond the attacker's control). The precise characters/trigger the parser mishandles are not detailed in the available sources. |
| Impact | Signals point to a real but not emergency-level issue. The reporter-supplied CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H, score 7.5) rates confidentiality, integrity and availability all High, which is unusually aggressive for a stored XSS (CWE-79); for browser-executed script the realistic impact and scope handling are debatable, so treat the 7.5 as a ceiling rather than a confirmed severity. Mitigating factors are material: AC:H plus the stated prerequisite that a non-default image delivery mode be enabled, plus UI:R (a victim must view an affected page), all reduce the practical attack surface, even though PR:N allows the malicious content to be submitted without authentication. KEV: not listed, so there is no confirmed active exploitation. EPSS: not provided in the input, so probabilistic exploitation likelihood cannot be stated. POC: a WPScan reference exists but is not verified as working exploit code. The vuln.today decision label is 'this_week', consistent with a patch-promptly posture rather than an act-now emergency. Net: a genuine, patch-this-week web-application vulnerability whose real-world risk is gated by the non-default configuration requirement and user interaction, not a widespread drive-by threat on default installs. |
| Exploit ScenarioDerived | On a site running WebP Express before 0.25.16 with a non-default image delivery mode enabled, an unauthenticated attacker submits crafted content containing attribute-breaking characters that the plugin's bundled HTML parser re-emits into element attributes without escaping. The payload is stored and later rendered, executing as script in the browser of any visitor who views the affected page - including a logged-in administrator, enabling session/admin-context actions. A public PoC reference exists (WPScan); it is not verified as working exploit code. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 22, 2026
Stored cross-site scripting in the WebP Express WordPress plugin before 0.25.16 lets unauthenticated visitors submit values that the plugin's bundled HTML parser later re-emits into element attributes without escaping, so the payload breaks out of the attribute context and executes in the browser of anyone who loads the affected page, including administrators. The vulnerable code path is only reached when a non-default image delivery mode is enabled; default installations do not exercise it, and the stored payload only fires when a victim views the page, which is why the assessed vector carries UI:R and AC:H despite PR:N. A public PoC reference exists in the WPScan entry but is not verified as working exploit code, and there is no CISA KEV confirmation of active exploitation; vendor patch 0.25.16 is available and the issue is prioritized as this_week rather than emergency-level.
RemediationAI
Update WebP Express to version 0.25.16 or later, which is the vendor-released fixed version per the WPScan advisory (https://wpscan.com/vulnerability/f44cb329-fb2e-4fb1-b878-8b52b0c769cc/); the fix is in the plugin release itself, so the standard WordPress admin-plugin update or a wp-cli plugin update is sufficient. As a compensating control, switch the plugin's image delivery mode back to the default setting, since the vulnerable parser path is only reached under a non-default delivery mode; the trade-off is loss of whatever delivery method the site was relying on (for example converted-asset HTML rewriting), which may change how images are served until the update can be applied. Reviewing stored content and plugin-generated markup for injected attributes is also advisable given the payload persists, but the definitive fix is the 0.25.16 upgrade. No additional compensating controls are specified in the available sources.
Affected VersionsENISA
Affected Packages
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
WebP Express is a WordPress image-optimization plugin that converts and serves WebP variants of media; in certain non-default image delivery modes it rewrites or parses generated HTML markup so that references point at converted assets. Its bundled HTML parser does not escape values that it re-emits into element attributes, the classic CWE-79 pattern of improper neutralization of input during web page generation, where an attacker-controlled value terminates the attribute quoting and injects new attributes or event handlers. Because the injected content is persisted and rendered from the plugin's own output, this is a stored (persistent) XSS rather than reflected. The CPE supplied is a placeholder namespace (cpe:2.3:a:unknown:webp_express) covering all versions of the plugin, with the EUVD entry narrowing the affected range to 0 through versions below 0.25.16; the exact characters or parser construct that is mishandled is not described in the available sources. The published CVSS 3.1 base of 7.5 (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H) is more severe than our assessed CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N, which treats the impact as scoped to the victim's browser session with limited confidentiality and integrity rather than full host compromise.
Know when Webp Express 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
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Unauthenticated remote submission (PR:N); non-default mode must be enabled, raising AC:H; stored script runs in the victim browser (S:C, UI:R) with limited C/I and no availability impact - hence lower than the reporter's C:H/I:H/A:H.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The WebP Express WordPress plugin before 0.25.16 does not escape values that its bundled HTML parser re-emits into element attributes when a non-default image delivery mode is enabled, allowing unauthenticated users to submit content that is stored and later executed as Cross-Site Scripting in the browser of any user viewing an affected page, including administrators.
Technical POC Analysis
CWE-79 (Improper Neutralization of Input During Web Page Generation - stored XSS).
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
A stored cross-site scripting vulnerability in the WebP Express WordPress plugin (versions before 0.25.16) could allow unauthenticated attackers to inject malicious scripts that execute when pages are viewed, potentially compromising administrator sessions and leading to site takeover. The vulnerability only affects configurations with a non-default image delivery mode enabled, and exploitation requires user interaction and is complex. While no active exploitation has been confirmed, a public proof-of-concept reference exists, and the vendor has released a patch (0.25.16). Leadership should prioritize patching this week due to the potential for administrative compromise and the plugin's use across the organization's WordPress sites.
Apply vendor patch.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Webp Express
View allThe webp-express plugin before 0.14.8 for WordPress has stored XSS. Rated medium severity (CVSS 5.4), this vulnerability
The webp-express plugin before 0.14.11 for WordPress has insufficient protection against arbitrary file reading. Rated h
EUVD-2026-108020
GHSA-3hr8-rx2p-fg8c
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB