Protected Posts Logout Button <= 1.4.5 - Authenticated (Admin+) Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.4.6
- Affected Plugin
- Protected Posts Logout Button
- Affected Version
<= 1.4.5- CVSS
- 4.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2023-25978
At a glance
CVE-2023-25978 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Protected Posts Logout Button WordPress plugin, affecting versions <= 1.4.5. It carries a CVSS score of 4.4 (reachable over the network). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 1.4.6; sites on affected versions should update now. Disclosed February 2023, reported by yuyudhn.
Vulnerability Overview
The Protected Posts Logout Button plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in versions up to, and including, 1.4.5 due to insufficient input sanitization and output escaping. This makes it possible for administrator-level 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, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Protected Posts Logout Button <= 1.4.5 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 Protected Posts Logout Button the fix is 1.4.6: builds <= 1.4.5 are affected, anything from 1.4.6 onward is not.
Remediation
Update to version 1.4.6, 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: Protected Posts Logout Button 1.4.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Protected Posts Logout Button
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C