WordPress security changelog
MEDIUM CVE-2022-1663 Modified

Stop Spam Comments: A security weakness

Stop Spam Comments is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 6.5 CVSS · contact@wpscan.com
NVD score 6.5 CVSS 3.1 · nvd@nist.gov
Component
Stop Spam Comments
Plugin slug
stop-spam-comments
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Aug 29, 2022
Weakness
CWE-200 — Exposure of Sensitive Information to an Unauthorized Actor
NVD-CWE-Other

This CVE was published Aug 29, 2022 and is one of 1 known issue for this plugin.

Update, patch or deactivate.

Update Stop Spam Comments to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

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 Stop Spam Comments WordPress plugin through 0.2.1.2 does not properly generate the Javascript access token for preventing abuse of comment section, allowing threat authors to easily collect the value and add it to the request.

NVD vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Primary and upstream sources