Wordpress Learning Management SystemWordPress extension · Vibethemes
CVE-2024-10470
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe WPLMS WordPress theme fails to validate file paths in readfile() and unlink() functions, allowing unauthenticated attackers to delete arbitrary files on the server. Deletion of critical files like wp-config.php enables full WordPress reconfiguration and remote code execution. The vulnerability affects all versions up to 4.962 and is exploitable even when the theme is not activated.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wordpress Learning Management SystemWordPress extension
< 4.963CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate WPLMS theme installation directoryCheck your WordPress themes folder (wp-content/themes/) for a folder named 'wplms' or similar WPLMS theme folderAffected if The wplms theme folder exists in the themes directory
-
Determine installed WPLMS theme versionOpen the style.css file within the WPLMS theme folder and look for the 'Version:' header in the file comments, or check theme.json if presentAffected if The version listed is lower than 4.963 (e.g., 4.962, 4.96, 4.9, etc.)
-
Verify WordPress installationConfirm this is a WordPress site by checking for wp-config.php in the web rootAffected if WordPress is installed and the vulnerable WPLMS theme is present regardless of activation status
-
Check for theme files with file operationsReview server access logs for suspicious requests containing '../' directory traversal patterns targeting wp-config.php or other critical filesAffected if Unusual patterns like '?action=delete&file=../../wp-config.php' appear in logs (optional forensic step)
Your environment is affected if the WPLMS theme version is below 4.963 and the theme files are present in the WordPress installation, regardless of whether the theme is currently activated.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.963
Update to a patched version of WPLMS if available; if no patch exists, remove the theme entirely. Restrict file permissions on wp-config.php and other critical files as a defense-in-depth measure.
WPLMS Learning Management System version 4.963
- 1. Backup your entire WordPress site (database and files) before making any changes
- 2. Download WPLMS Learning Management System theme version 4.963 from the official source (themeforest.net or theme author)
- 3. Navigate to WordPress Admin Dashboard > Appearance > Themes
- 4. Deactivate the WPLMS theme temporarily if active
- 5. Delete the existing WPLMS theme (or replace by uploading the new version)
- 6. Upload and install the WPLMS version 4.963 theme
- 7. Reactivate the theme if needed
- 8. Verify the vulnerability is patched by checking that the readfile and unlink functions now properly validate file paths
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wordpress Learning Management System
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10470 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-10470 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data