# CVE-2021-20831: Cross-site request forgery in OG Tags

> A CSRF vulnerability in the OG Tags plugin allows attackers to hijack administrator sessions and perform unintended actions.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 13 Oct 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-w35x-3cc7-37pc

## What is CVE-2021-20831?

CVE-2021-20831 is a high-severity vulnerability in Mario Valney OG Tags, published on 13 Oct 2021. 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 OG Tags versions prior to 2.0.2 allows a remote attacker to hijack the authentication of administrators and unintended operation may be performed via unspecified vectors.

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

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

It affects 1 product.


Products: Og Tags Project Og Tags.

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

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

## Is CVE-2021-20831 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-20831 is a high-severity vulnerability in Mario Valney OG Tags, published on 13 Oct 2021. 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-20831 in the wild and no public exploit code.

Affected product: Mario Valney OG Tags. 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-20831/ (Markdown: https://insights.sbomify.com/CVE-2021-20831/index.md)
```

## Sources

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

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