dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-67888

HIGH · 7.3 CVSS v3.1 Published 2026-05-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An issue was discovered in Control Web Panel (CWP) before 0.9.8.1209. User input passed via the "key" GET parameter to /admin/index.php (when the "api" parameter is set) is not properly sanitized before being used to execute OS commands. This can be exploited by unauthenticated attackers to inject and execute arbitrary OS commands with the privileges of root on the web server. Softaculous or SitePad must be present.

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 confidence

CWP versions before 0.9.8.1208 contain an OS command injection vulnerability in /admin/index.php. The 'key' GET parameter is not sanitized when the 'api' parameter is present, allowing unauthenticated attackers to execute arbitrary OS commands as root. The vulnerability is only exploitable when Softaculous or SitePad is installed.

MitigationUpgrade CWP to version 0.9.8.1209 or later. As an interim control, restrict network access to /admin/index.php and disable or remove Softaculous/SitePad if not required.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify CWP installation and version
    Check for CWP by looking for its control panel files or running: cat /usr/local/cwpsrv/version 2>/dev/null || rpm -qa | grep -i cwp
    Affected if CWP is installed and version is lower than 0.9.8.1208 (e.g., 0.9.8.1207 or earlier)
  2. Verify Softaculous or SitePad is installed
    Check for Softaculous: ls /usr/local/cwpsrv/var/services/softaculous 2>/dev/null; Check for SitePad: ls /usr/local/cwpsrv/var/services/sitedpad 2>/dev/null; Or check via CWP admin panel under 'Plugins' or 'Applications'
    Affected if Either Softaculous or SitePad is installed on the server (this is required for the exploit to work)
  3. Confirm /admin/index.php is network accessible
    Verify the CWP admin interface is exposed: curl -s -I https://YOUR_SERVER_IP:2087/admin/index.php 2>/dev/null | head -5; Check if firewall allows port 2087 (or 2086) from untrusted networks
    Affected if The /admin/index.php endpoint is reachable from the network where attackers could send requests (unauthenticated access is possible)
  4. Check for suspicious activity in admin access logs
    Review /usr/local/cwpsrv/logs/access_log or /var/log/httpd/access_log for unusual requests to /admin/index.php with 'api' and 'key' parameters; Example: grep 'admin/index.php.*api.*key' /usr/local/cwpsrv/logs/access_log
    Affected if There are log entries showing requests to /admin/index.php with 'api' and 'key' parameters that you did not initiate

You are affected if CWP version is below 0.9.8.1208 AND Softaculous or SitePad is installed AND the admin interface is network-accessible, putting you at risk of unauthenticated root command injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade CWP to version 0.9.8.1209 or later. As an interim control, restrict network access to /admin/index.php and disable or remove Softaculous/SitePad if not required.

Recommended fix Moderate confidence

CWP version 0.9.8.1209 or later

  1. 1. Verify the current CWP version by checking the admin panel or running: cwpctl version
  2. 2. Confirm that Softaculous or SitePad is installed (this is a prerequisite for the vulnerability)
  3. 3. Backup all critical data and configurations before performing the upgrade
  4. 4. Update CWP to version 0.9.8.1209 or later using the official update mechanism: cwpctl update or through the admin panel
  5. 5. After update, verify the new version is 0.9.8.1209 or higher using: cwpctl version
  6. 6. Test that the /admin/index.php API functionality works correctly post-update
  7. 7. Review CWP logs to ensure no unauthorized access occurred during the update window
Caveat Review CWP release notes for version 0.9.8.1209 for any configuration or feature changes that may affect your setup

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67888 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-67888 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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