# CVE-2017-20090: Global Content Blocks Plugin cross-site request forgery

> A cross-site request forgery vulnerability in the Global Content Blocks Plugin 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:** 23 Jun 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-wc24-384w-7j97

## What is CVE-2017-20090?

CVE-2017-20090 is a medium-severity vulnerability in unspecified Global Content Blocks Plugin, published on 23 Jun 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 was found in Global Content Blocks Plugin 2.1.5. It has been declared as problematic. This vulnerability affects unknown code. The manipulation leads to cross-site request forgery. The attack can be initiated remotely.

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

## Which versions are affected by CVE-2017-20090?

It affects 1 product.


Products: Global Content Blocks Project Global Content Blocks.

## How do I fix CVE-2017-20090?

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

## Is CVE-2017-20090 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-20090 and fix it if it is affected.

What it is: CVE-2017-20090 is a medium-severity vulnerability in unspecified Global Content Blocks Plugin, published on 23 Jun 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-2017-20090 exists.

Affected product: unspecified Global Content Blocks Plugin. 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-2017-20090/ (Markdown: https://insights.sbomify.com/CVE-2017-20090/index.md)
```

## Sources

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

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