# CVE-2023-51473: WordPress TerraClassifieds Plugin <= 2.0.3 is vulnerable to Arbitrary File Upload

> Attackers can upload malicious files to execute arbitrary code on WordPress sites using the TerraClassifieds plugin.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Dec 2023
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-wfv4-v3vj-4vq5

## What is CVE-2023-51473?

CVE-2023-51473 is a critical vulnerability in Pixelemu TerraClassifieds – Simple Classifieds Plugin, published on 29 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unrestricted Upload of File with Dangerous Type vulnerability in Pixelemu TerraClassifieds – Simple Classifieds Plugin.This issue affects TerraClassifieds – Simple Classifieds Plugin: from n/a through 2.0.3.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2023-51473?

It affects 1 product.


Products: Pixelemu Terraclassifieds.

## How do I fix CVE-2023-51473?

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

## Is CVE-2023-51473 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-51473 and fix it if it is affected.

What it is: CVE-2023-51473 is a critical vulnerability in Pixelemu TerraClassifieds – Simple Classifieds Plugin, published on 29 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-51473 in the wild and no public exploit code.

Affected product: Pixelemu TerraClassifieds – Simple Classifieds Plugin. 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-2023-51473/ (Markdown: https://insights.sbomify.com/CVE-2023-51473/index.md)
```

## Sources

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

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