VDZ Verification <= 1.3.12 - Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.4
- Affected Plugin
- VDZ VERIFICATION (Custom Meta Tags)
- Affected Version
<= 1.3.12- CVSS
- 5.5Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE pending
At a glance
This record tracks a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the VDZ VERIFICATION (Custom Meta Tags) WordPress plugin, affecting versions <= 1.3.12. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). The issue is fixed in version 1.4; sites on affected versions should update now. Disclosed July 2021.
Vulnerability Overview
The VDZ Verification plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Meta Tag settings in versions up to, and including, 1.3.12 due to insufficient input sanitization and output escaping. This makes it possible for authenticated Admin+ attackers 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, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in VDZ VERIFICATION (Custom Meta Tags) <= 1.3.12 takes a caller who can reach the endpoint. 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 VDZ VERIFICATION (Custom Meta Tags) the fix is 1.4: builds <= 1.3.12 are affected, anything from 1.4 onward is not.
Remediation
Update to version 1.4, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to VDZ VERIFICATION (Custom Meta Tags): WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: VDZ VERIFICATION (Custom Meta Tags) 1.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C