Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain contributor-level account
-
DeliveryInsert Twenty20 shortcode with malicious 'offset' value
-
ExploitStore unsanitized payload in page
-
ExecutionHigher-privileged user views page
-
PersistScript executes in victim browser session
-
ImpactHijack session or perform admin actions
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 | Requires an authenticated WordPress account at contributor level or above on a site running Twenty20 Image Before-After ≤2.0.5; the attacker must be able to insert the Twenty20 shortcode and supply a crafted 'offset' attribute, which is stored without sufficient sanitization/escaping. Execution is deferred and conditional: the injected script only fires when another user (e.g., an editor or admin) subsequently views the injected page, so impact depends on a privileged user visiting the content. Limiting factors: authentication is mandatory (not remote-unauthenticated), so sites that restrict contributor accounts or disable open registration materially reduce exposure; no special non-default plugin configuration is otherwise required beyond use of the vulnerable shortcode. |
| Impact | This is a moderate-severity stored XSS (CWE-79) with a provided CVSS 3.1 vector of CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N (6.4). The network vector and low attack complexity are offset by the requirement for PR:L (contributor-level authentication per CVSS and corroborated by the description), which meaningfully narrows the attacker pool to users already granted authoring privileges on the WordPress site. The scope change (S:C) and Low confidentiality/integrity impacts reflect script execution in the browser context of other users (e.g., editors/admins reviewing the content), which is the real danger - potential session/cookie theft or admin-action abuse via the victim's authenticated session. No EPSS score, SSVC decision, KEV listing, or POC was supplied in the input; absence of these should not be read as low risk, only as missing telemetry. There is no public exploit identified at time of analysis and no evidence of active exploitation, so this is a real but not urgent priority: patch in normal cadence, prioritizing multi-author sites where contributor accounts are plentiful or self-registration is open. Conflict to note: none significant - the CVSS PR:L aligns with the description's 'contributor-level access and above' requirement. |
| Exploit ScenarioDerived | A low-privileged contributor account (self-registered or compromised) crafts a post using the Twenty20 shortcode and injects a malicious payload into the 'offset' attribute, which is stored without proper sanitization or output escaping. When an editor or administrator previews or views the resulting page, the script executes in their authenticated browser context, enabling session hijacking or actions on their behalf. No public exploit code was identified at time of analysis, and the network vector with low complexity makes exploitation straightforward for any user holding contributor rights. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 03, 2026
Stored cross-site scripting in the WordPress plugin Twenty20 Image Before-After (all versions up to and including 2.0.5) allows authenticated users with contributor-level access or above to inject arbitrary JavaScript through the 'offset' attribute of the plugin's shortcode; the injected script is stored in a post and executes when another user, such as an editor or administrator, later views that page. The CVSS 3.1 vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N (6.4), reflecting a network-reachable, low-privilege, no-user-interaction attack with changed scope but limited confidentiality and integrity impact, and authentication is mandatory, so sites that restrict contributor accounts or disable open registration materially reduce exposure. No CISA KEV entry or public exploit code was identified at time of analysis, and the plugin's Trac changeset indicates a 2.0.6 tag superseding 2.0.5.
RemediationAI
Upgrade the Twenty20 Image Before-After plugin to the 2.0.6 tag or later: the plugin's Trac changeset (https://plugins.trac.wordpress.org/changeset?reponame=&new=3712833%40twenty20%2Ftags%2F2.0.6&old=3712169%40twenty20%2Ftags%2F2.0.5) shows 2.0.6 created from 2.0.5, so the fix should be applied by updating through the WordPress plugin admin or by deploying the tagged release; Wordfence's advisory is at https://www.wordfence.com/threat-intel/vulnerabilities/id/ae21be88-494f-4b24-95e1-97367d252cf7?source=cve. Where immediate upgrade is not possible, reduce exposure by tightening the contributor role (remove the ability to publish or submit shortcode-bearing content, or set new posts to pending review with manual inspection), disabling open user registration and pruning dormant or untrusted contributor accounts, since the attack requires an authenticated contributor-level account; a plugin such as a shortcode/content sanitizer that strips arbitrary HTML attributes from post content also blunts the payload, with the trade-off that it may break legitimate plugin shortcodes site-wide. Because the injected script is stored, scan existing posts for Twenty20 shortcodes containing non-numeric or otherwise malformed 'offset' values and remove or re-save those posts after patching, and treat any account that authored such content as potentially compromised.
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
The vulnerability is a classic stored XSS (CWE-79) in the shortcode handling layer of a WordPress plugin. WordPress shortcodes are parsed from post content and their attributes passed to a handler function; in Twenty20 Image Before-After, the shortcode handler in inc/twenty20-shortcode.php (lines 8, 90 and 95 of the 2.0.4 tag are cited in the references) takes the user-supplied 'offset' attribute and emits it into the generated HTML without adequate sanitization or output escaping, instead of casting it to an integer (e.g. absint()) or escaping it with esc_attr(). Because the value is persisted with the post rather than reflected immediately, the payload survives and executes in the browser context of any subsequent viewer who can see the page, which is why the CVSS vector marks scope as changed (S:C) even though the direct confidentiality and integrity impacts are limited (C:L/I:L). Affected code is present in all builds covered by the CPE identifier cpe:2.3:a:zayedbaloch:twenty20_image_before-after:*:*:*:*:*:*:*:* and in the EUVD range ≤2.0.5.
Know when Wordpress Plugin 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:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Contributor authentication required so PR:L; stored payload needs no attacker interaction (UI:N) and executes in other users' context giving S:C with Low C/I and no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Twenty20 Image Before-After plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'offset' Shortcode Attribute in all versions up to, and including, 2.0.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
EUVD-2026-91967
GHSA-265f-7jp6-5v2f
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB