# CVE-2021-4275: katlings pyambic-pentameter cross-site request forgery

> A cross-site request forgery vulnerability in the pyambic-pentameter library allows remote attackers to perform unauthorized actions.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/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:** 21 Dec 2022
- **Updated:** 14 Apr 2025
- **Also known as:** GHSA-52x4-qwpg-c64f

## What is CVE-2021-4275?

CVE-2021-4275 is a medium-severity vulnerability in katlings pyambic-pentameter, published on 21 Dec 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

A vulnerability, which was classified as problematic, was found in katlings pyambic-pentameter. Affected is an unknown function. The manipulation leads to cross-site request forgery. It is possible to launch the attack remotely. The name of the patch is 974f21aa1b2527ef39c8afe1a5060548217deca8. It is recommended to apply a patch to fix this issue. VDB-216498 is the identifier assigned to this vulnerability.

Weakness: CWE-352 (Cross-Site Request Forgery), CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2021-4275?

It affects 1 product.


Products: Pyambic-Pentameter Project Pyambic-Pentameter.

## How do I fix CVE-2021-4275?

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

## Is CVE-2021-4275 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-4275 and fix it if it is affected.

What it is: CVE-2021-4275 is a medium-severity vulnerability in katlings pyambic-pentameter, published on 21 Dec 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: There is no known exploitation of CVE-2021-4275 in the wild and no public exploit code.

Affected product: katlings pyambic-pentameter. 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-2021-4275/ (Markdown: https://insights.sbomify.com/CVE-2021-4275/index.md)
```

## Sources

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

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