CVE-2026-96575 ivijanstefan CVE debrief

Who should care

Defenders responsible for WordPress installations with the Transliterator plugin should assess exposure and prioritize updating the plugin to a fixed version. They should also monitor for suspicious comment activity to detect potential attacks and implement additional security measures to prevent cross-site scripting.

Why it matters

The Transliterator plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content. Defenders should prioritize updating the plugin and monitoring for suspicious activity.

• Unauthenticated attackers can inject web scripts that execute when a user accesses an injected page
• The payload survives WordPress comment save-time sanitization
• Defenders need to update the plugin to a fixed version to prevent exploitation
• Monitoring for suspicious comment activity is necessary to detect potential attacks

Technical summary

The Transliterator – Multilingual and Multi-script Text Conversion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content due to insufficient input sanitization and output escaping. This allows unauthenticated attackers to inject web scripts that execute when a user accesses an injected page. The vulnerability exists in all versions up to, and including, 2.5.8 of the Transliterator plugin. The payload survives WordPress comment save-time sanitization because the tags and attributes used are permitted by the core comment kses allow-list. Defenders should prioritize updating the plugin to a fixed version and monitor for suspicious comment activity.

Defensive priority

Defenders should prioritize updating the plugin to a fixed version and monitor for suspicious comment activity.

Recommended defensive actions

• Update the Transliterator plugin to a fixed version
• Monitor for suspicious comment activity
• Implement additional security measures to prevent cross-site scripting
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability exists in all versions up to, and including, 2.5.8 of the Transliterator plugin. The payload survives WordPress comment save-time sanitization because the tags and attributes used are permitted by the core comment kses allow-list.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.