CVE-2018-25335
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 · uneditedWordPress Plugin Peugeot Music 1.0 contains an arbitrary file upload vulnerability that allows unauthenticated attackers to upload malicious files by sending POST requests to the upload.php endpoint. Attackers can upload files with arbitrary extensions by manipulating the 'name' parameter to execute code from the uploads directory.
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 Peugeot Music WordPress plugin 1.0 contains an unauthenticated arbitrary file upload vulnerability in the upload.php endpoint. Attackers can manipulate the 'name' parameter in POST requests to upload files with arbitrary extensions, including executable PHP files, directly to the uploads directory and achieve 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
- 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.
-
Identify if Peugeot Music plugin is installedNavigate to WordPress admin dashboard > Plugins and look for 'Peugeot Music' in the installed plugins list, or inspect the /wp-content/plugins/ directory for a folder named 'peugeot-music' or similarAffected if The plugin appears in the installed plugins list or its directory exists in wp-content/plugins/
-
Determine the plugin versionIn the WordPress plugins admin page, click on the plugin details for Peugeot Music and check the version field; alternatively, read the main plugin PHP file and look for a version comment or constantAffected if The installed version is 1.0 (or any version where upload.php is present without proper authentication and file validation)
-
Locate the vulnerable upload.php endpointCheck if the file upload.php exists within the plugin directory by accessing /wp-content/plugins/[plugin-folder]/upload.php or using file system inspectionAffected if The upload.php file exists in the plugin directory, indicating the vulnerable endpoint is present
-
Verify unauthenticated access to the upload endpointAttempt a HEAD or OPTIONS request to the upload.php URL without providing any authentication cookies or credentialsAffected if The endpoint responds without requiring authentication (HTTP 200 or other success response rather than 401/403)
-
Inspect uploads directory for suspicious filesExamine the /wp-content/uploads/ directory (and subdirectories) for recently created .php, .phtml, or other executable files that were not intentionally uploaded through legitimate WordPress media functionalityAffected if Unexpected PHP files or other executable scripts are present in the uploads directory, especially if created recently and not associated with known legitimate uploads
You are affected if the Peugeot Music plugin version 1.0 is installed and the upload.php endpoint exists in your environment, allowing unauthenticated file uploads to your WordPress site.
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 remove or disable the Peugeot Music plugin until a patched version with proper authentication, file type validation, and filename sanitization is available; if the plugin is essential, implement temporary server-side controls to block executable file uploads.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-25335 — 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-2018-25335 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