dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 7 Feb 2023.
WebpanelApplication · Control Webpanel

CVE-2022-44877

CRITICAL · 9.8 CVSS v3.1 Published 2023-01-05
Fix available
A fix is available. Upgrade to 0.9.8.1147 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit 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
login/index.php in CWP (aka Control Web Panel or CentOS Web Panel) 7 before 0.9.8.1147 allows remote attackers to execute arbitrary OS commands via shell metacharacters in the login parameter.

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

This is a pre-authentication command injection vulnerability in CWP (Control Web Panel) version 7 before 0.9.8.1147. Attackers can inject arbitrary OS commands via shell metacharacters in the login parameter of login/index.php. The 9.8 CVSS score reflects the critical severity of unauthenticated remote code execution.

MitigationUpgrade CWP to version 0.9.8.1147 or later. If immediate patching is not feasible, restrict network access to the admin panel and implement WAF rules to filter shell metacharacters in HTTP parameters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WebpanelApplication
Affected:< 0.9.8.1147

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 checks

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

  1. Confirm CWP installation
    Check if Control Web Panel is installed on the system by looking for CWP service files, directories such as /usr/local/cwpsrv, or by accessing the control panel login page via web browser on port 2031 (default CWP port).
    Affected if CWP is installed and running on the server.
  2. Identify installed CWP version
    Locate the CWP version file - common locations include /usr/local/cwpsrv/htdocs/resources/admin/include/version.php or check the CWP admin interface footer for the version number. Compare your installed version against the affected range: versions before 0.9.8.1147.
    Affected if Installed CWP version is less than 0.9.8.1147.
  3. Verify vulnerable script exists
    Check if the file login/index.php exists in the CWP web root directory. This is the specific script where the command injection vulnerability resides.
    Affected if The login/index.php file exists in the CWP web directory.
  4. Confirm login interface accessibility
    Determine if the CWP login page is accessible over the network by attempting to access http://<your-server-ip>:2031/login/index.php or the standard CWP login URL.
    Affected if The CWP login interface is network-accessible (not blocked by firewall or internal-only configuration).

The environment is affected if CWP is installed with a version lower than 0.9.8.1147 and the login interface is accessible, as the command injection vulnerability in login/index.php can be exploited.

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
Upgrade available Upgrade to 0.9.8.1147 or later
Fixed in 0.9.8.1147
Interim mitigation

Upgrade CWP to version 0.9.8.1147 or later. If immediate patching is not feasible, restrict network access to the admin panel and implement WAF rules to filter shell metacharacters in HTTP parameters.

Recommended fix High confidence

CWP (Control Web Panel) version 0.9.8.1147 or later

  1. Backup your CWP configuration and data before proceeding with the update
  2. Update CWP (Control Web Panel) to version 0.9.8.1147 or later using the official update mechanism (typically via the CWP admin panel or command line update script)
  3. Verify the update was successful by checking the CWP version in the admin interface
  4. Confirm that the login/index.php component has been patched and no longer accepts shell metacharacters in the login parameter
  5. Test that the login functionality works correctly after the update
Caveat Standard web panel upgrade - test in staging first if possible

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

Fix this in Webpanel Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-44877 — 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-2022-44877 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