CVE-2026-88792
WordPress · Dictionary
The Dictionary WordPress plugin through version 1.0 is vulnerable to stored Cross-Site Scripting (XSS) due to insufficient input validation, allowing unauthenticated attackers to execute arbitrary scripts.
Executive summary
The Dictionary WordPress plugin is vulnerable to unauthenticated stored Cross-Site Scripting, which could allow attackers to execute malicious scripts in the context of a victim's browser session.
Vulnerability
This is a stored Cross-Site Scripting (CWE-79) vulnerability that occurs because the plugin lacks proper authorization, sanitization, and escaping mechanisms when processing dictionary entries. An unauthenticated attacker can inject arbitrary web scripts that execute whenever a user views the compromised entry.
Business impact
The exploitation of this vulnerability poses a significant risk to user session integrity and application security. With a CVSS score of 8.8, this flaw allows attackers to steal session cookies, redirect users to malicious domains, or perform unauthorized actions on behalf of authenticated administrators, potentially leading to a full site compromise.
Remediation
Immediate Action: Since no patch is currently available, administrators should immediately deactivate and remove the Dictionary plugin from their WordPress environment until a secure version is released.
Proactive Monitoring: Security teams should audit WordPress user activity logs and monitor for unusual script injections or modifications within the dictionary database tables.
Compensating Controls: Deploy a Web Application Firewall (WAF) with robust XSS filtering rules to inspect incoming traffic and block malicious payloads directed at the dictionary entry submission endpoints.
Exploitation status
Public Exploit Available: Unknown.
Analyst recommendation
Given the high severity of this vulnerability and the lack of a verified patch, immediate removal of the affected software is the only reliable method to mitigate risk. Organizations should prioritize removing the plugin and evaluating alternative solutions that adhere to modern secure coding practices.
More WordPress CVEs all →
History
- Disclosed CVE record published
- Collected by CVE Brief No CVSS score yet; tracked as early warning
- Held for re-check analysis graded thin
- Analyst report written
Sources
Originally found and disclosed by Pablo González Pérez, Francisco José Ramírez Vicente, and Iñigo Sánchez Enciso, with WPScan (coordinator), per the CVE Program record.