Subscribe To Comments Reloaded: A security weakness
Subscribe To Comments Reloaded is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 240119.
- Component
- Subscribe To Comments Reloaded
- Plugin slug
subscribe-to-comments-reloaded- Affected
- <= 240119
- Safe version
> 240119- Published
- May 05, 2026
This CVE was published May 05, 2026 and is one of 4 known issues for this plugin.
Update, patch or deactivate.
Update Subscribe To Comments Reloaded to a release after 240119, or disable and remove it until a fixed version is available.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Subscribe To Comments Reloaded plugin for WordPress is vulnerable to unauthorized modification of data due to a leaked secret key and usage of a weak hash generation algorithm in all versions up to, and including, 240119. This makes it possible for unauthenticated attackers to extract the global key from any public post page, forge authorization keys and manage comment subscription preferences for arbitrary users
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N