# CVE-2024-10470: WPLMS Learning Management System for WordPress <= 4.962 - Unauthenticated Arbitrary File Read and Deletion

> Unauthenticated attackers can read and delete arbitrary files, potentially leading to remote code execution by deleting critical configuration files.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 9 Nov 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-pqm3-x6xp-m28q

## What is CVE-2024-10470?

CVE-2024-10470 is a critical path traversal vulnerability in VibeThemes WPLMS Learning Management System for WordPress, WordPress LMS, published on 9 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WPLMS Learning Management System for WordPress, WordPress LMS theme for WordPress is vulnerable to arbitrary file read and deletion due to insufficient file path validation and permissions checks in the readfile and unlink functions in all versions up to, and including, 4.962. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). The theme is vulnerable even when it is not activated.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Vibethemes Wordpress Learning Management System.

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

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

## Is CVE-2024-10470 being exploited?

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

Public exploit code:

- WPLMS Learning Management System for WordPress <= 4.962 – Unauthenticated Arbitrary File Read and Deletion (github_poc): https://github.com/RandomRobbieBF/CVE-2024-10470

## Other vulnerabilities in VibeThemes WPLMS Learning Management System for WordPress, WordPress LMS

- [CVE-2024-56046](https://insights.sbomify.com/CVE-2024-56046/): WordPress WPLMS plugin <= 1.9.9 - Unauthenticated Arbitrary File Upload vulnerability (critical 10.0)
- [CVE-2024-56050](https://insights.sbomify.com/CVE-2024-56050/): WordPress WPLMS plugin < 1.9.9.5.3 - Subscriber+ Arbitrary File Upload vulnerability (critical 9.9)
- [CVE-2024-56052](https://insights.sbomify.com/CVE-2024-56052/): WordPress WPLMS plugin < 1.9.9.5.2 - Student+ Arbitrary File Upload vulnerability (critical 9.9)
- [CVE-2024-56057](https://insights.sbomify.com/CVE-2024-56057/): WordPress WPLMS plugin < 1.9.9.5.2 - Arbitrary File Upload vulnerability (critical 9.9)
- [CVE-2024-56043](https://insights.sbomify.com/CVE-2024-56043/): WordPress WPLMS plugin <= 1.9.9 - Unauthenticated Privilege Escalation vulnerability (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-10470 is a critical path traversal vulnerability in VibeThemes WPLMS Learning Management System for WordPress, WordPress LMS, published on 9 Nov 2024. 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-2024-10470 in the wild and no public exploit code.

Affected product: VibeThemes WPLMS Learning Management System for WordPress, WordPress LMS. 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-10470/ (Markdown: https://insights.sbomify.com/CVE-2024-10470/index.md)
```

## Sources

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

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