# CVE-2024-38736: WordPress Realtyna Organic IDX plugin <= 4.14.13 - Arbitrary File Upload vulnerability

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

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jul 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-pw74-hq2f-c2j4

## What is CVE-2024-38736?

CVE-2024-38736 is a critical vulnerability in Realtyna Organic IDX plugin, published on 12 Jul 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unrestricted Upload of File with Dangerous Type vulnerability in Realtyna Realtyna Organic IDX plugin allows Code Injection.This issue affects Realtyna Organic IDX plugin: from n/a through 4.14.13.

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

## Which versions are affected by CVE-2024-38736?


## How do I fix CVE-2024-38736?

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

## Is CVE-2024-38736 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-38736 and fix it if it is affected.

What it is: CVE-2024-38736 is a critical vulnerability in Realtyna Organic IDX plugin, published on 12 Jul 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-38736 in the wild and no public exploit code.

Affected product: Realtyna Organic IDX 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-2024-38736/ (Markdown: https://insights.sbomify.com/CVE-2024-38736/index.md)
```

## Sources

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

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