# CVE-2020-9514: Missing authorization in n/a

> A logged-in subscriber can delete arbitrary posts and modify or create new posts due to missing authorization checks in the IMPress for IDX Broker plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hc7g-786w-w835

## What is CVE-2020-9514?

CVE-2020-9514 is a medium-severity missing authorization vulnerability in n/a, published on 7 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in the IMPress for IDX Broker plugin before 2.6.2 for WordPress. wrappers.php allows a logged-in user (with the Subscriber role) to permanently delete arbitrary posts and pages, create new posts with arbitrary subjects, and modify the subjects of existing posts and pages (via create_dynamic_page and delete_dynamic_page).

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Idxbroker Impress for Idx Broker.

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

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

## Is CVE-2020-9514 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-44047](https://insights.sbomify.com/CVE-2024-44047/): WordPress IMPress for IDX Broker plugin <= 3.2.2 - Cross Site Scripting (XSS) vulnerability (medium 6.5)
- [CVE-2020-11512](https://insights.sbomify.com/CVE-2020-11512/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-9514 is a medium-severity missing authorization vulnerability in n/a, published on 7 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-9514 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-2020-9514/ (Markdown: https://insights.sbomify.com/CVE-2020-9514/index.md)
```

## Sources

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

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