# CVE-2022-1663: Stop Spam Comments <= 0.2.1.2 - Access Token Bypass

> Attackers can bypass comment spam protection by easily obtaining the predictable JavaScript access token in the Stop Spam Comments plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-38w5-52h3-rfmp

## What is CVE-2022-1663?

CVE-2022-1663 is a medium-severity vulnerability in Unknown Stop Spam Comments, published on 29 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-1663?

It affects 1 product.


Products: Stop Spam Comments Project Stop Spam Comments.

## How do I fix CVE-2022-1663?

No fix has been published for CVE-2022-1663 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-1663 being exploited?

There is no known exploitation of CVE-2022-1663 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1663 and fix it if it is affected.

What it is: CVE-2022-1663 is a medium-severity vulnerability in Unknown Stop Spam Comments, published on 29 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1663 in the wild and no public exploit code.

Affected product: Unknown Stop Spam Comments. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-1663/ (Markdown: https://insights.sbomify.com/CVE-2022-1663/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-1663
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-1663
- OSV: https://osv.dev/vulnerability/CVE-2022-1663

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-1663/
Summaries are generated and may contain mistakes; the official description above is the record.