Subscribe To Comments Reloaded <= 220725 - Unauthenticated Sensitive Information Exposure
Strategic Overview
- Status
- Patched in 240119
- Affected Plugin
- Subscribe To Comments Reloaded
- Affected Version
<= 220725- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2024-31249
At a glance
CVE-2024-31249 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Subscribe To Comments Reloaded WordPress plugin, affecting versions <= 220725. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 240119; sites on affected versions should update now. Disclosed April 2024, reported by Joshua Chan.
Vulnerability Overview
The Subscribe To Comments Reloaded plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 220725 via log files. This makes it possible for unauthenticated attackers to extract sensitive data from log files.
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, and no interaction from a victim user.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in Subscribe To Comments Reloaded <= 220725 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Subscribe To Comments Reloaded the fix is 240119: builds <= 220725 are affected, anything from 240119 onward is not.
Remediation
Update to version 240119, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Subscribe To Comments Reloaded 240119 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Subscribe To Comments Reloaded
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C