CVE Analysis 3 min read

CVE-2026-6518: The CMP – Coming Remote code execution Enables Remote Exploitation

CVE-2026-6518 CVSS 8.8 HIGH vulnerability analysis

CVE-2026-6518 is a high severity vulnerability (CVSS 8.8) identified in the National Vulnerability Database. The CMP – Coming Soon & Maintenance Plugin by NiteoThemes plugin for WordPress is vulnerable to arbitrary file upload and remote code execution in all versions up to, and including, 4.1.16 via the `cmp_theme_update_install` AJAX action. This is due to the function only checking for the

What This Vulnerability Is

The CMP – Coming Soon & Maintenance Plugin by NiteoThemes plugin for WordPress is vulnerable to arbitrary file upload and remote code execution in all versions up to, and including, 4.1.16 via the `cmp_theme_update_install` AJAX action. This is due to the function only checking for the `publish_pages` capability (available to Editors and above) instead of `manage_options` (Administrators only), combined with a lack of proper validation on the user-supplied file URL and no verification of the downloaded file's content before extraction. This makes it possible for authenticated attackers, with Administrator-level access and above, to force the server to download and extract a malicious ZIP file from a remote attacker-controlled URL into a web-accessible directory (`wp-content/plugins/cmp-premium-themes/`), resulting in remote code execution. Due to the lack of a nonce for Editors, they are unable to exploit this vulnerability.

The National Vulnerability Database assigned this issue a CVSS base score of 8.8, placing it in the HIGH category. The identifier CVE-2026-6518 was published on 2026-04-18T05:16:24.377.

CVE Identifier
CVE-2026-6518
CVSS Base Score
8.8 / 10.0 (HIGH)
Published
2026-04-18T05:16:24.377
NVD Entry
https://nvd.nist.gov/vuln/detail/CVE-2026-6518
MITRE Entry
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-6518

Who Is Affected

Based on the vulnerability data published by NVD, the following products and configurations are identified as affected:

  • Specific affected products are listed in the NVD entry. Review the CPE data for your stack.

If your organization uses any of the above, this vulnerability applies to your environment. Even if your specific version is not listed, review the full CPE match data to confirm.

What to Do About It

Here is what we recommend, in order of priority:

  1. Check your exposure. Determine whether the affected software or component is present in your environment. Asset inventories and software composition analysis (SCA) tools are the fastest route.
  2. Apply the patch. If a vendor patch or updated version is available, apply it. Check the references below for vendor advisories.
  3. Mitigate if patching is not immediate. If you cannot patch right now, evaluate whether network segmentation, access control changes, or configuration adjustments reduce the attack surface for this specific vulnerability.
  4. Monitor for exploitation. Check whether proof-of-concept exploit code exists. The CISA Known Exploited Vulnerabilities catalog tracks actively exploited CVEs.
  5. Document your response. Record what you checked, when you patched, and what residual risk remains. This matters for compliance and for incident response if this vulnerability is exploited later.

Why This Matters for Companies Without Security Teams

A CVSS score of 8.8 means this vulnerability is straightforward to exploit, likely to cause significant damage, or both. For startups and small companies operating without a dedicated security team, vulnerabilities at this severity level represent real operational risk rather than theoretical concern.

The challenge is not awareness. Vulnerability databases are public. The challenge is triage: understanding whether a given CVE affects your specific stack, and knowing what to do about it before an attacker does. If you lack the internal capacity to perform that assessment, an external review of your exposure is a concrete next step.

Sherlock Forensics provides vulnerability assessment and penetration testing for organizations that need to understand their attack surface without building a full internal security function.

References and Further Reading