CVE-2025-60218
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 · uneditedSubscriber Arbitrary File Upload in PT Luxa Addons <= 1.2.2 versions.
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 · moderate confidenceA critical arbitrary file upload vulnerability in PT Luxa Addons plugin versions 1.2.2 and below allows authenticated users with Subscriber-level privileges to upload arbitrary files to the server, potentially leading to remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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.
-
Identify PT Luxa Addons plugin versionAccess your WordPress admin panel, navigate to Plugins > Installed Plugins, locate PT Luxa Addons, and read the version number displayed beneath the plugin name. Alternatively, inspect the plugin directory (wp-content/plugins/pt-luxa-addons/) and open the main PHP file or readme.txt to find the Version: field in the plugin header.Affected if The installed version is 1.2.2 or any version lower than 1.2.2.
-
Confirm subscriber-level user accounts existIn WordPress admin, go to Users > All Users and review the list of users. Check the Role column to identify any accounts assigned the Subscriber role.Affected if At least one user account with the Subscriber role exists in the WordPress installation.
-
Verify file upload functionality is accessible to subscribersInspect the PT Luxa Addons plugin code, specifically looking for any file upload handlers, AJAX endpoints, or form processing logic that accepts file submissions. Check if these endpoints use current_user_can() or similar capability checks that permit subscriber-level access.Affected if The plugin contains file upload functionality that does not enforce capability checks higher than subscriber-level, or has no capability checks at all.
-
Check for suspicious uploaded filesSearch the wp-content/uploads/ directory and any plugin-specific upload directories for files with executable extensions (.php, .phtml, .php5, .php7, .exe, .sh, .js) that were recently uploaded and do not match expected file types.Affected if Unexpected executable files are found in upload directories, especially if uploaded by users with subscriber-level accounts.
You are affected if PT Luxa Addons version is 1.2.2 or below AND subscriber-level user accounts exist in your WordPress installation.
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.
From vendor dataImmediately update PT Luxa Addons to the latest patched version. Until patched, disable the plugin or restrict subscriber user registration to prevent exploitation.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60218 — 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-2025-60218 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