Duplicate Page or Post <= 1.5.0 - Missing Authorization to Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.5.1
- Affected Plugin
- Duplicate Page or Post
- Affected Version
<= 1.5.0- CVSS
- 6.4Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2021-25075
At a glance
CVE-2021-25075 is a medium-severity Missing Authorization vulnerability in the Duplicate Page or Post WordPress plugin, affecting versions <= 1.5.0. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 1.5.1; sites on affected versions should update now. Disclosed January 2022, reported by Krzysztof Zając.
Vulnerability Overview
The Duplicate Page or Post WordPress plugin before 1.5.1 does not have any authorisation and has a flawed CSRF check in the wpdevart_duplicate_post_parametrs_save_in_db AJAX action, allowing any authenticated users, such as subscriber to call it and change the plugin's settings, or perform such attack via CSRF. Furthermore, due to the lack of escaping, this could lead to Stored Cross-Site Scripting issues
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-862: Missing Authorization
Reaching this weakness in Duplicate Page or Post <= 1.5.0 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Duplicate Page or Post the fix is 1.5.1: builds <= 1.5.0 are affected, anything from 1.5.1 onward is not.
Remediation
Update to version 1.5.1, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Duplicate Page or Post 1.5.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C