# CVE-2017-6819: Cross-site request forgery in n/a

> A CSRF vulnerability in WordPress Press This allows attackers to trigger resource-intensive outbound requests, potentially causing denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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:** Yes
- **Published:** 12 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-6819, GHSA-34f4-j2gj-cg3x, UBUNTU-CVE-2017-6819

## What is CVE-2017-6819?

CVE-2017-6819 is a medium-severity vulnerability in Wordpress Wordpress, published on 12 Mar 2017. 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

In WordPress before 4.7.3, there is cross-site request forgery (CSRF) in Press This (wp-admin/includes/class-wp-press-this.php), leading to excessive use of server resources. The CSRF can trigger an outbound HTTP request for a large file that is then parsed by Press This.

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

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

It affects 1 product.


Products: Wordpress Wordpress.

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

Upgrade to a fixed version.

## Is CVE-2017-6819 being exploited?

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

## Other vulnerabilities in Wordpress Wordpress

- [CVE-2026-63030](https://insights.sbomify.com/CVE-2026-63030/): WordPress Core Interpretation Conflict (critical 9.8, exploited in the wild)
- [CVE-2026-87902](https://insights.sbomify.com/CVE-2026-87902/): WordPress Core Remote File Inclusion (high 8.1, exploited in the wild)
- [CVE-2026-60137](https://insights.sbomify.com/CVE-2026-60137/): WordPress Core SQL Injection (medium 5.9, exploited in the wild)
- [CVE-2012-2399](https://insights.sbomify.com/CVE-2012-2399/): Cross-site scripting in n/a (critical 10.0)
- [CVE-2012-2400](https://insights.sbomify.com/CVE-2012-2400/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6819 is a medium-severity vulnerability in Wordpress Wordpress, published on 12 Mar 2017. 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-2017-6819 in the wild and no public exploit code.

Affected product: Wordpress Wordpress. 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-6819/ (Markdown: https://insights.sbomify.com/CVE-2017-6819/index.md)
```

## Sources

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

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