# CVE-2019-6027: Cross-site request forgery in WP Spell Check

> Remote attackers can hijack administrator authentication in WP Spell Check via CSRF, potentially taking over admin accounts.

- **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:** 26 Dec 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-652g-mfhf-979g

## What is CVE-2019-6027?

CVE-2019-6027 is a high-severity vulnerability in WP Spell Check, published on 26 Dec 2019. 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 WP Spell Check 7.1.9 and earlier allows remote attackers to hijack the authentication of administrators via unspecified vectors.

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

## Which versions are affected by CVE-2019-6027?

It affects 1 product.


Products: Wpspellcheck Wpspellcheck.

## How do I fix CVE-2019-6027?

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

## Is CVE-2019-6027 being exploited?

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

## Other vulnerabilities in WP Spell Check

- [CVE-2024-22143](https://insights.sbomify.com/CVE-2024-22143/): WordPress WP Spell Check Plugin <= 9.17 is vulnerable to Cross Site Request Forgery (CSRF) (medium 5.4)
- [CVE-2022-2658](https://insights.sbomify.com/CVE-2022-2658/): WP Spell Check < 9.13 - Admin+ Stored Cross-Site Scripting (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-6027 and fix it if it is affected.

What it is: CVE-2019-6027 is a high-severity vulnerability in WP Spell Check, published on 26 Dec 2019. 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-2019-6027 in the wild and no public exploit code.

Affected product: WP Spell Check. 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-2019-6027/ (Markdown: https://insights.sbomify.com/CVE-2019-6027/index.md)
```

## Sources

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

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