Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged authenticated account
-
DeliveryInject script into Typing Text input
-
ExploitPayload stored unneutralized
-
ExecutionVictim views affected page
-
ImpactScript executes in victim browser context
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 authenticated account with sufficient privilege to submit input handled by the Typing Text plugin (PR:L, consistent with a contributor/author-level WordPress role) on a site running the plugin at version 2.2.0 or earlier. The stored payload only fires when a second user renders the affected page (UI:R), so a victim must view the injected content for impact to occur. These factors - required authentication and required victim interaction - limit the attack to actors who already have a foothold on the site and meaningfully constrain opportunistic mass exploitation. The exact plugin input field or feature that fails to neutralize the input is not described in the available sources. |
| Impact | This is a moderate-severity stored XSS (CVSS 6.5, CWE-79) reported by Patchstack against the bPlugins 'Typing Text' WordPress plugin through version 2.2.0. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L indicates a network-reachable, low-complexity issue that requires an authenticated low-privileged user (PR:L) to plant the payload and a victim to then view the affected content (UI:R), with a scope change (S:C) reflecting that injected script executes in another user's browser context. No EPSS score, CISA KEV listing, or confirmed working exploit was supplied; the single reference is the Patchstack vulnerability-database entry, which is a PoC/advisory reference, not verified working exploit code. The vuln.today decision label is 'this_month', not act_now or emergency, so this should be prioritized for routine patching rather than treated as an active-exploitation crisis. The combination of required authentication plus victim interaction, limited (Low) impact on confidentiality/integrity/availability, and a low-footprint niche plugin keeps real-world risk modest despite the network attack vector. No KEV or EPSS data was provided, so widespread opportunistic exploitation cannot be inferred and is not indicated. |
| Exploit ScenarioDerived | A user with at least contributor/author-level access to the WordPress site submits a crafted payload into an input processed by the Typing Text plugin, which stores it without proper neutralization. When an administrator or another visitor later renders the page containing that typing-text content, the script executes in their browser (UI:R, S:C). A public PoC reference exists on Patchstack; 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 26, 2026
Stored cross-site scripting in the bPlugins 'Typing Text - Give your texts many typing effects' WordPress plugin affects every release through 2.2.0, allowing an authenticated user with contributor- or author-level privileges to persist malicious markup that executes in another user's browser when the injected content is rendered. The assessed vector (CVSS 6.5, AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L) reflects that the attacker needs an existing account on the target site and that a second user must view the affected page before the payload fires, which limits the flaw to actors who already hold a foothold on the installation rather than remote unauthenticated intruders. No public exploit code or CISA KEV entry is associated with this issue at time of analysis, and the EPSS-style priority assigned by vuln.today places it in the current-month remediation queue rather than the emergency tier.
RemediationAI
The supplied intelligence does not list a fixed version, so operators should consult the Patchstack advisory for the patched release and upgrade the 'Typing Text - Give your texts many typing effects' plugin past 2.2.0 as soon as that version is published; the CVE remains associated with all versions through 2.2.0. Until an upgrade is available, the practical exposure reduction follows directly from the assessed prerequisites: the attack requires an authenticated account able to submit plugin-handled input (PR:L, contributor/author level), so restricting who holds content-creation roles on the site, and auditing or removing untrusted author and contributor accounts, removes the injection path, at the cost of narrowing editorial workflow. Because the stored payload fires only when a second user renders the page (UI:R), reviewing recently authored posts and pages that embed typing-effect content before publishing them further limits delivery, though it does not remove the underlying defect. No vendor-stated workaround is documented in the available sources, and updating once a patched release exists is the complete fix.
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 flaw is a classic CWE-79 improper neutralization of input during web page generation in a WordPress plugin. The plugin accepts content that is later emitted into HTML pages without adequate encoding or sanitization; because the malicious data is stored server-side and replayed to every visitor of the affected page, the payload runs in the security context of the WordPress site's origin. The CVSS scope-change flag (S:C) captures the fact that the injected script escapes the plugin's own component boundary and can act against the surrounding site and its users, although the confidentiality, integrity and availability sub-scores are all Low. The CPE entry cpe:2.3:a:bplugins:typing_text_-_give_your_texts_many_typing_effects:*:*:*:*:*:*:*: is version-agnostic, consistent with the advisory covering all releases through 2.2.0. Authentication requirements are confirmed unauthenticated-not: the vector carries PR:L, matching a contributor- or author-level WordPress role in the independent assessment. The specific plugin input field, shortcode attribute or block parameter that fails to neutralize input is not described in the available sources, and the trigger mechanism should not be assumed from the CWE class alone.
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:R/S:C/C:L/I:L/A:L
Stored XSS needs a low-privileged authenticated user to inject (PR:L) and a victim to view it (UI:R); script runs in the victim's context (S:C) with limited C/I/A impact.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in bPlugins Typing Text - Give your texts many typing effects text-typing allows Stored XSS.This issue affects Typing Text - Give your texts many typing effects: from n/a through 2.2.0.
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 AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
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
EUVD-2026-110044
GHSA-hhw6-cj52-7w4w
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB