# CVE-2020-13700: acf-to-rest-api plugin insecure direct object reference (IDOR) via permalink manipulation

> An insecure direct object reference in the acf-to-rest-api WordPress plugin allows attackers to read sensitive data from the wp_options table.

- **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:** 24 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r345-x8hr-2r9p

## What is CVE-2020-13700?

CVE-2020-13700 is a high-severity vulnerability in n/a, published on 24 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the acf-to-rest-api plugin through 3.1.0 for WordPress. It allows an insecure direct object reference via permalinks manipulation, as demonstrated by a wp-json/acf/v3/options/ request that reads sensitive information in the wp_options table, such as the login and pass values.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2020-13700?

2 open source packages ship an affected version, including airesvsg/acf-to-rest-api. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `airesvsg/acf-to-rest-api` | Packagist | All versions to 3.1.0 | None |
| `airesvsg/acf-to-rest-api` | Packagist | All versions to 3.1.0 | None |

Products: Acf to Rest Api Project Acf to Rest Api.

## How do I fix CVE-2020-13700?

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

## Is CVE-2020-13700 being exploited?

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

Public exploit code:

- WordPress acf-to-rest-api <=3.1.0 - Insecure Direct Object Reference (nuclei): http/cves/2020/CVE-2020-13700.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-13700 and fix it if it is affected.

What it is: CVE-2020-13700 is a high-severity vulnerability in n/a, published on 24 Jun 2020. 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-2020-13700 exists.

Affected packages and fixed versions:
- airesvsg/acf-to-rest-api (Packagist): affected all versions up to 3.1.0; no fix listed
- airesvsg/acf-to-rest-api (Packagist): affected all versions up to 3.1.0; no fix listed

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-2020-13700/ (Markdown: https://insights.sbomify.com/CVE-2020-13700/index.md)
```

## Sources

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

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