# CVE-2024-22287: WordPress Better Anchor Links Plugin <= 1.7.5 is vulnerable to Cross Site Request Forgery (CSRF)

> Attackers can trick users into executing malicious scripts via CSRF in the Better Anchor Links WordPress plugin.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **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:** 31 Jan 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-5mwr-c944-45q4

## What is CVE-2024-22287?

CVE-2024-22287 is a high-severity vulnerability in Luděk Melichar Better Anchor Links, published on 31 Jan 2024. 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

Cross-Site Request Forgery (CSRF) vulnerability in Luděk Melichar Better Anchor Links allows Cross-Site Scripting (XSS).This issue affects Better Anchor Links: from n/a through 1.7.5.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2024-22287?

It affects 1 product.


Products: Ludek Better Anchor Links.

## How do I fix CVE-2024-22287?

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

## Is CVE-2024-22287 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22287 and fix it if it is affected.

What it is: CVE-2024-22287 is a high-severity vulnerability in Luděk Melichar Better Anchor Links, published on 31 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-22287 in the wild and no public exploit code.

Affected product: Luděk Melichar Better Anchor Links. 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-2024-22287/ (Markdown: https://insights.sbomify.com/CVE-2024-22287/index.md)
```

## Sources

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

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