Skip to main content
CVE-2026-115250VulnerabilityPublished

The Text Typing WordPress plugin before 2.2.2 does not properly sanitize and escape a block attribute before storing

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-115250· High

Not known to be exploited : upgrade to 2.2.2 soon.

Data as of 4 Nov 2026, 07:30 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 2.2.2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

What to do

Upgrade Text Typing (WordPress plugin) to 2.2.2.

Affected software

ProductAffectedFixed in
Text TypingAffected
  • <2.2.2
Fixed in
  • 2.2.2

AI-suggested

Upgrade the Text Typing WordPress plugin to version 2.2.2 or later where this vulnerability is fixed. No other mitigation guidance is provided. Since the plugin is not a cloud service, manual update is required.

Description

The Text Typing WordPress plugin versions before 2.2.2 contain a vulnerability where a block attribute is not properly sanitized and escaped before storage and output. This flaw allows users with Contributor role or higher to inject stored cross-site scripting (XSS) payloads that execute in the browsers of visitors to affected pages.

References

Community reviews

Loading reviews…