# CVE-2018-20968: Cross-site request forgery in n/a

> A Cross-Site Request Forgery vulnerability in the wp-ultimate-exporter plugin allows attackers to trick users into performing unintended actions.

- **Severity:** High 8.8 (`CVSS:3.0/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:** 14 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qjrm-3323-m349

## What is CVE-2018-20968?

CVE-2018-20968 is a high-severity vulnerability in n/a, published on 14 Aug 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

The wp-ultimate-exporter plugin before 1.4.2 for WordPress has CSRF.

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

## Which versions are affected by CVE-2018-20968?

It affects 1 product.


Products: Smackcoders Ultimate Exporter.

## How do I fix CVE-2018-20968?

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

## Is CVE-2018-20968 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-11000](https://insights.sbomify.com/CVE-2016-11000/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20968 and fix it if it is affected.

What it is: CVE-2018-20968 is a high-severity vulnerability in n/a, published on 14 Aug 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-2018-20968 in the wild and no public exploit code.

Affected product: n/a. 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-2018-20968/ (Markdown: https://insights.sbomify.com/CVE-2018-20968/index.md)
```

## Sources

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

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