Word Replacer <= 0.4 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'Replacement' Parameter
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Word Replacer
- Affected Version
<= 0.4- CVSS
- 4.4Medium
- Weakness type
- CWE-20 · Improper Input Validation
- CVE
CVE-2026-3620
At a glance
CVE-2026-3620 is a medium-severity Improper Input Validation vulnerability in the Word Replacer WordPress plugin, affecting versions <= 0.4. It carries a CVSS score of 4.4 (reachable over the network). Exploitation requires an authenticated account at Administrator level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed June 2026, reported by san6051.
Vulnerability Overview
The Word Replacer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'replacement' parameter in all versions up to, and including, 0.4. This is due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Administrator-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user.
CWE-20: Improper Input Validation
Word Replacer <= 0.4 carries this weakness at replacement, and reaching it takes an account at Administrator level or above. Improper input validation means the application accepts input without confirming it has the form, type or range the code downstream assumes.
The concrete impact depends on where the unvalidated value lands, which is why records in this class range from cosmetic bugs to full compromise. No fixed build of this plugin is recorded for Word Replacer yet, so installs running <= 0.4 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
An attacker needs Administrator 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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C