CVE-2022-27131
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 · uneditedAn arbitrary file upload vulnerability at /zbzedit/php/zbz.php in zbzcms v1.0 allows attackers to execute arbitrary code via a crafted PHP file.
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 confidenceAn arbitrary file upload vulnerability exists in zbzcms v1.0 at the endpoint /zbzedit/php/zbz.php. Attackers can upload malicious PHP files without proper validation, enabling remote code execution on the affected server.
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 installationSearch for zbzcms files in the web directory. Look for typical zbzcms directories such as /zbzedit/, /admin/, or check for zbzcms-specific configuration files and templates.Affected if zbzcms is present on the server
-
Verify zbzcms version is 1.0Locate the version identifier in zbzcms. Check files like version.php, index.php, or any about/readme file within the installation. Compare the installed version against the affected version 1.0.Affected if The installed version is exactly 1.0
-
Check if vulnerable endpoint existsVerify if the file /zbzedit/php/zbz.php exists on the web server. Inspect the zbzcms installation directory structure to confirm the presence of this specific file path.Affected if The file /zbzedit/php/zbz.php exists on the server
-
Verify endpoint is web-accessibleAttempt an HTTP/HTTPS request to the /zbzedit/php/zbz.php endpoint. Confirm whether the endpoint responds and is accessible without authentication.Affected if The endpoint is reachable from the web without authentication
The environment is affected if zbzcms version 1.0 is installed and the /zbzedit/php/zbz.php endpoint exists and is web-accessible, allowing potential unauthenticated file uploads.
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 dataDisable or remove the vulnerable /zbzedit/php/zbz.php endpoint immediately. If the functionality is required, implement strict file type validation (allowlist approach), verify file headers/magic bytes, store uploads outside webroot, and disable PHP execution in upload directories.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27131 — 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-27131 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