# CVE-2022-3097: LBStopAttack < 1.1.3 - Arbitrary Settings Update via CSRF

> Attackers can force users to disable LBStopAttack plugin protections via CSRF due to missing nonces in settings saving.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Oct 2022
- **Updated:** 7 May 2025
- **Also known as:** GHSA-rjwc-8f5q-7v36

## What is CVE-2022-3097?

CVE-2022-3097 is a medium-severity vulnerability in Unknown Plugin LBstopattack, published on 25 Oct 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Plugin LBstopattack WordPress plugin before 1.1.3 does not use nonces when saving its settings, making it possible for attackers to conduct CSRF attacks. This could allow attackers to disable the plugin's protections.

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

It affects 1 product.


Products: Laubrotel Lbstopattack.

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

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

## Is CVE-2022-3097 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3097 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3097 is a medium-severity vulnerability in Unknown Plugin LBstopattack, published on 25 Oct 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3097 exists.

Affected product: Unknown Plugin LBstopattack. 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-3097/ (Markdown: https://insights.sbomify.com/CVE-2022-3097/index.md)
```

## Sources

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

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