# CVE-2024-34381: WordPress PropertyHive plugin <= 2.0.10 - Cross Site Scripting (XSS) vulnerability

> Attackers can inject malicious scripts into PropertyHive plugin pages, potentially stealing user data or hijacking sessions.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 May 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-4qhm-36g2-5mv9

## What is CVE-2024-34381?

CVE-2024-34381 is a medium-severity cross-site scripting vulnerability in PropertyHive, published on 6 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in PropertyHive allows Stored XSS.This issue affects PropertyHive: from n/a through 2.0.10.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Wp-Property-Hive Propertyhive.

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

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

## Is CVE-2024-34381 being exploited?

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

## Other vulnerabilities in PropertyHive

- [CVE-2024-8490](https://insights.sbomify.com/CVE-2024-8490/): PropertyHive <= 2.0.19 - Cross-Site Request Forgery via save_account_details (high 8.8)
- [CVE-2024-23513](https://insights.sbomify.com/CVE-2024-23513/): WordPress PropertyHive Plugin <= 2.0.5 is vulnerable to PHP Object Injection (high 8.7)
- [CVE-2024-29923](https://insights.sbomify.com/CVE-2024-29923/): WordPress PropertyHive plugin <= 2.0.8 - Reflected Cross Site Scripting (XSS) vulnerability (high 7.1)
- [CVE-2023-22706](https://insights.sbomify.com/CVE-2023-22706/): WordPress PropertyHive Plugin <= 1.5.48 is vulnerable to Cross Site Scripting (XSS) (high 7.1)
- [CVE-2023-29172](https://insights.sbomify.com/CVE-2023-29172/): WordPress PropertyHive Plugin <= 1.5.46 is vulnerable to Cross Site Scripting (XSS) (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-34381 is a medium-severity cross-site scripting vulnerability in PropertyHive, published on 6 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-34381 in the wild and no public exploit code.

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

## Sources

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

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