Ezoic <= 2.8.8 - Authenticated (Admin+) Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.8.9
- Affected Plugin
- Ezoic
- Affected Version
<= 2.8.8- CVSS
- 7.2High
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2022-41315
At a glance
CVE-2022-41315 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Ezoic WordPress plugin, affecting versions <= 2.8.8. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 2.8.9; sites on affected versions should update now. Disclosed November 2022, reported by José Aguilera.
Vulnerability Overview
The Ezoic plugin for WordPress is vulnerable to Stored Cross-Site Scripting via settings in versions up to, and including, 2.8.8 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrative privileges, to inject malicious web scripts into a page.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Ezoic <= 2.8.8 takes an account at Admin level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Ezoic the fix is 2.8.9: builds <= 2.8.8 are affected, anything from 2.8.9 onward is not.
Remediation
Update to version 2.8.9, or a newer patched version
How does WordSec protect against this?
An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Ezoic 2.8.9 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C