Post Pay Counter <= 2.789 - Reflected Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.790
- Affected Plugin
- Post Pay Counter
- Affected Version
<= 2.789- CVSS
- 6.1Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2023-47673
At a glance
CVE-2023-47673 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Post Pay Counter WordPress plugin, affecting versions <= 2.789. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.790; sites on affected versions should update now. Disclosed November 2023, reported by LEE SE HYOUNG.
Vulnerability Overview
The Post Pay Counter plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'orderby' parameter in versions up to, and including, 2.789 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
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 privileges on the target site.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Post Pay Counter <= 2.789 carries this weakness at orderby, and reaching it 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 Post Pay Counter the fix is 2.790: builds <= 2.789 are affected, anything from 2.790 onward is not.
Remediation
Update to version 2.790, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Post Pay Counter: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Post Pay Counter 2.790 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Post Pay Counter
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C