# CVE-2021-39312: True Ranker <= 2.2.2 Directory Traversal/Arbitrary File Read

> Attackers can read arbitrary files, including sensitive configuration files, via a directory traversal vulnerability in the True Ranker WordPress plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Dec 2021
- **Updated:** 31 Jan 2025
- **Also known as:** GHSA-2mm8-gjg2-whmx

## What is CVE-2021-39312?

CVE-2021-39312 is a high-severity path traversal vulnerability in True Ranker, published on 14 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The True Ranker plugin <= 2.2.2 for WordPress allows arbitrary files, including sensitive configuration files such as wp-config.php, to be accessed via the src parameter found in the ~/admin/vendor/datatables/examples/resources/examples.php file.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Trueranker True Ranker.

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

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

## Is CVE-2021-39312 being exploited?

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

Public exploit code:

- WordPress Plugin The True Ranker 2.2.2 - Arbitrary File Read (Unauthenticated) (exploitdb)
- Exploit-WordPress Plugin The True Ranker 2.2.2 - Arbitrary File Read (github_poc): https://github.com/root-wav/wordpress-true-ranker-cve-2021-39312
- WordPress True Ranker <2.2.4 - Local File Inclusion (nuclei): http/cves/2021/CVE-2021-39312.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2021-39312 is a high-severity path traversal vulnerability in True Ranker, published on 14 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-39312 exists.

Affected product: True Ranker. 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-39312/ (Markdown: https://insights.sbomify.com/CVE-2021-39312/index.md)
```

## Sources

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

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