# CVE-2024-1315: Classified Listing <= 3.0.4 - Cross-Site Request Forgery to Account Takeover via rtcl_update_user_account

> Attackers can hijack administrator accounts via CSRF by changing credentials, requiring admin interaction to exploit this WordPress plugin vulnerability.

- **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:** 9 Apr 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-fjjf-hfph-8mm9

## What is CVE-2024-1315?

CVE-2024-1315 is a high-severity vulnerability in techlabpro1 Classified Listing – AI-Powered Classified ads & Business Directory Plugin, published on 9 Apr 2024. 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

The Classified Listing – Classified ads & Business Directory Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.0.4. This is due to missing or incorrect nonce validation on the 'rtcl_update_user_account' function. This makes it possible for unauthenticated attackers to change the administrator user's password and email address via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. This locks the administrator out of the site and prevents them from resetting their password, while granting the attacker access to their account.

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

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

It affects 1 product.


Products: Radiustheme Classified Listing.

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

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

## Is CVE-2024-1315 being exploited?

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

## Other vulnerabilities in techlabpro1 Classified Listing – AI-Powered Classified ads & Business Directory Plugin

- [CVE-2024-1352](https://insights.sbomify.com/CVE-2024-1352/): Classified Listing – Classified ads & Business Directory Plugin <= 3.0.4 - Missing Authorization (medium 6.5)
- [CVE-2024-7888](https://insights.sbomify.com/CVE-2024-7888/): Classified Listing – Classified ads & Business Directory Plugin <= 3.1.7 - Missing Authorization (medium 6.3)
- [CVE-2022-2654](https://insights.sbomify.com/CVE-2022-2654/): Classima < 2.1.11 - Reflected Cross-Site Scripting (medium 6.1)
- [CVE-2022-2655](https://insights.sbomify.com/CVE-2022-2655/): Classified Listing Pro < 2.0.20 - Reflected Cross-Site Scripting (medium 6.1)
- [CVE-2023-37387](https://insights.sbomify.com/CVE-2023-37387/): WordPress Classified Listing Plugin <= 2.4.5 is vulnerable to Cross Site Request Forgery (CSRF) (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1315 is a high-severity vulnerability in techlabpro1 Classified Listing – AI-Powered Classified ads & Business Directory Plugin, published on 9 Apr 2024. 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-1315 in the wild and no public exploit code.

Affected product: techlabpro1 Classified Listing – AI-Powered Classified ads & Business Directory 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-1315/ (Markdown: https://insights.sbomify.com/CVE-2024-1315/index.md)
```

## Sources

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

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