CVE-2025-32118
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in NiteoThemes CMP – Coming Soon & Maintenance cmp-coming-soon-maintenance allows Using Malicious Files.This issue affects CMP – Coming Soon & Maintenance: from n/a through <= 4.1.14.
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 confidenceThe CMP – Coming Soon & Maintenance WordPress plugin before version 4.1.15 contains an unrestricted file upload vulnerability allowing attackers to upload malicious files (e.g., PHP shells) to the server, potentially achieving remote code execution. The lack of proper file type validation on uploaded files enables this critical flaw.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Confirm CMP plugin installationLog into WordPress admin panel, navigate to Plugins > Installed Plugins, and search for 'CMP - Coming Soon & Maintenance' or 'CMP'Affected if The plugin is not listed in the installed plugins
-
Identify installed plugin versionIn the Plugins list, locate the CMP plugin and note the version number displayed beneath the plugin nameAffected if The version shown is lower than 4.1.15 (e.g., 4.1.14, 4.1.10, etc.)
-
Check if upload functionality is accessibleNavigate to the plugin settings page (usually under Settings > CMP or a dedicated CMP menu) and locate any file upload features such as logo upload, background image upload, or custom page asset uploadAffected if The plugin provides any file upload interface and the installed version is below 4.1.15
-
Verify upload endpoint is reachableUse browser developer tools or curl to inspect network requests when accessing the plugin upload features; check if the wp-content/uploads directory is writable and accessibleAffected if Upload forms are present and the plugin version is below 4.1.15
You are affected if the CMP - Coming Soon & Maintenance plugin is installed with any version prior to 4.1.15 and the plugin's file upload functionality is accessible on your 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 dataUpdate to version 4.1.15 or later when available; meanwhile, disable the plugin or restrict upload capabilities at the web server level. Implement web application firewall rules to block executable file uploads.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32118 — 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-32118 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