# CVE-2024-39623: WordPress ListingPro theme <= 2.9.4 - Cross Site Request Forgery (CSRF) to Account Takeover vulnerability

> A CSRF vulnerability in the ListingPro WordPress theme allows attackers to bypass authentication and take over user accounts.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Jan 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-46v9-776w-chff

## What is CVE-2024-39623?

CVE-2024-39623 is a high-severity vulnerability in CridioStudio ListingPro, published on 2 Jan 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-Site Request Forgery (CSRF) vulnerability in CridioStudio ListingPro listingpro allows Authentication Bypass.This issue affects ListingPro: from n/a through <= 2.9.4.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Cridio Listingpro.

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

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

## Is CVE-2024-39623 being exploited?

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

## Other vulnerabilities in CridioStudio ListingPro

- [CVE-2020-36719](https://insights.sbomify.com/CVE-2020-36719/): ListingPro - WordPress Directory & Listing Theme < 2.6.1 - Arbitrary Plugin Installation, Activation and Deactivation (critical 9.8)
- [CVE-2024-38795](https://insights.sbomify.com/CVE-2024-38795/): WordPress ListingPro plugin <= 2.9.4 - Unauthenticated SQL Injection vulnerability (critical 9.3)
- [CVE-2024-39622](https://insights.sbomify.com/CVE-2024-39622/): WordPress ListingPro theme <= 2.9.4 - Unauthenticated SQL Injection vulnerability (critical 9.3)
- [CVE-2024-39619](https://insights.sbomify.com/CVE-2024-39619/): WordPress ListingPro plugin <= 2.9.4 - Unauthenticated Local File Inclusion vulnerability (critical 9.0)
- [CVE-2024-39620](https://insights.sbomify.com/CVE-2024-39620/): WordPress ListingPro plugin <= 2.9.4 - SQL Injection vulnerability (high 8.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-39623 is a high-severity vulnerability in CridioStudio ListingPro, published on 2 Jan 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-39623 in the wild and no public exploit code.

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

## Sources

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

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