CVE-2022-27126
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 · uneditedzbzcms v1.0 was discovered to contain a SQL injection vulnerability via the art parameter at /include/make.php.
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 confidencezbzcms v1.0 contains a SQL injection vulnerability in the art parameter at /include/make.php. An attacker can inject malicious SQL queries through this parameter to manipulate database queries, potentially leading to unauthorized data access, modification, or complete database compromise. The critical CVSS score of 9.8 indicates this is exploitable over the network with low attack complexity and no authentication required.
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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm zbzcms installationLocate the zbzcms application on your system by searching for its installation directory or known file structure (typically includes /include/ directory)Affected if zbzcms is installed on the system
-
Identify installed versionCheck the version number of your zbzcms installation. Common locations include a version file, about page, or configuration file. Compare against the affected version: 1.0Affected if The installed version is exactly 1.0
-
Verify vulnerable file existsCheck if the file /include/make.php exists in your zbzcms installation directoryAffected if The file /include/make.php is present
-
Check for art parameter exposureExamine if the web application exposes the art parameter through the /include/make.php endpoint. This is typically accessible via HTTP GET or POST requests to that scriptAffected if The art parameter is accepted and processed by make.php without sanitization
-
Inspect SQL query handling in make.phpReview the source code of /include/make.php and locate where the art parameter is used in database queries. Look for dynamic SQL construction (string concatenation) rather than parameterized queriesAffected if The art parameter is directly interpolated into SQL queries without prepared statements or input validation
You are affected if you have zbzcms version 1.0 installed with the /include/make.php file present and the art parameter accessible without sanitization or prepared statement protection.
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 dataReplace dynamic SQL queries with parameterized queries (prepared statements) in /include/make.php for the art parameter, and implement proper input validation as a defense-in-depth measure. If a patched version is available, upgrade to that version.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27126 — 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-2022-27126 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