dbcve.org
Control CenterApplication · Asus

CVE-2022-26669

MEDIUM · 6.5 CVSS v3.1 Published 2022-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
ASUS Control Center is vulnerable to SQL injection. An authenticated remote attacker with general user privilege can inject SQL command to specific API parameters to acquire database schema or access data.

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

ASUS Control Center contains a SQL injection vulnerability in its API endpoints. An authenticated attacker with standard user privileges can inject malicious SQL commands through specific API parameters to extract database schema information and sensitive data. The vulnerability is exploitable remotely and requires only low-privilege authentication.

MitigationImplement parameterized queries or prepared statements for all database interactions to prevent SQL injection. Additionally, apply least-privilege principles to database accounts used by the application.

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
Control CenterApplication
Affected:= 1.4.2.5

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 ASUS Control Center installation
    Locate the application in the program menu, check Windows Services, or look in typical installation paths such as C:\Program Files\ASUS\Control Center or C:\ASUS\Control Center
    Affected if The application is not installed on the system
  2. Identify installed version
    Check the application version through the About/Help menu in the GUI, examine versioninfo.xml or similar version files in the installation directory, or query the Windows Registry under HKLM\SOFTWARE\ASUS\Control Center for the Version value
    Affected if The installed version is exactly 1.4.2.5
  3. Verify API endpoint accessibility
    Attempt to access the API endpoints used by the application, typically found under /api/ or /api/v1/ paths on the web server port (commonly 443 or 8080). Use browser developer tools or curl to inspect API responses
    Affected if API endpoints are exposed and reachable from the network
  4. Check authentication configuration
    Review the application user management settings to confirm whether standard (low-privilege) user accounts can access the API functionality. Verify if default or weak credentials exist
    Affected if Standard user accounts with limited privileges can authenticate to the API endpoints

The environment is affected if ASUS Control Center version 1.4.2.5 is installed and its API endpoints are accessible to authenticated users with standard privileges.

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

Implement parameterized queries or prepared statements for all database interactions to prevent SQL injection. Additionally, apply least-privilege principles to database accounts used by the application.

Recommended fix Moderate confidence

ASUS Control Center version 1.4.2.7 or later

  1. 1. Identify the current ASUS Control Center version installed in your environment
  2. 2. Download ASUS Control Center version 1.4.2.7 or later from the official ASUS support website
  3. 3. Before upgrading, backup the current configuration and database
  4. 4. Stop the ASUS Control Center services
  5. 5. Install the updated version (1.4.2.7 or later) using the official installer
  6. 6. Verify the upgrade by checking the version number in the Control Panel or About section
  7. 7. Test that the affected API endpoints are now properly sanitizing input
  8. 8. Restart the ASUS Control Center services

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

Fix this in Control Center Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing4.0 h
  • Review / QA2.0 h
22.0 hours of engineering $3,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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