CVE-2025-60218 WordPress PT Luxa Addons Plugin <= 1.2.2 - Arbitrary File Upload Vulnerability
Critical 9.9
Published
Updated
Check this codebase for CVE-2025-60218 and fix it if it is affected.
What it is: CVE-2025-60218 is a critical vulnerability in WPLocker PT Luxa Addons, published on 17 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-60218 in the wild and no public exploit code.
Affected product: WPLocker PT Luxa Addons. 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-2025-60218/ (Markdown: https://insights.sbomify.com/CVE-2025-60218/index.md)
A subscriber can upload arbitrary files, potentially leading to remote code execution on the WordPress site.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-60218?
CVE-2025-60218 is a critical vulnerability in WPLocker PT Luxa Addons, published on 17 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Subscriber Arbitrary File Upload in PT Luxa Addons <= 1.2.2 versions.
Weakness: CWE-434
Which versions are affected by CVE-2025-60218?
How do I fix CVE-2025-60218?
No fix has been published for CVE-2025-60218 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-60218 being exploited?
There is no known exploitation of CVE-2025-60218 in the wild and no public exploit code.
Sources
Also known as GHSA-qh4g-gvjg-jmqr.