CVE-2026-96575: Transliterator (WordPress plugin) · Cross-site Scripting
Affects Transliterator (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ivijanstefanTransliterator – Multilingual and Multi-script Text Conversion | Affected
| Fixed in– |
AI-suggested
Users should monitor the vendor's advisory for updates. Until a fix is available, consider disabling comments or restricting comment content to trusted users to reduce exposure. Avoid relying solely on WordPress core sanitization as it does not prevent this issue due to allowed tags and plugin-specific placeholders.
Description
The Transliterator – Multilingual and Multi-script Text Conversion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content via Predictable {rstr_keep} Placeholder in all versions up to, and including, 2.5.8 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload survives WordPress comment save-time sanitization because the tags and attributes used (such as a[title] and code) are permitted by the core comment kses allow-list, and the literal characters comprising the plugin's shortcode markers and placeholder tokens are not stripped.
References
- wordfence.com/threat-intel/vulnerabilities/id/f31bf520-2006-496b-b487-62faea679cf6?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/serbian-transliteration/tags/2.5.8/classes/controller.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/serbian-transliteration/tags/2.5.8/classes/controller.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/serbian-transliteration/tags/2.5.8/classes/controller.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&old=3714692%40serbian-transliteration&new=3714692%40serbian-transliteration (opens in a new tab)