CVE-2022-27125
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 stored cross-site scripting (XSS) vulnerability via the neirong parameter at /php/ajax.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 stored cross-site scripting (XSS) vulnerability in the neirong parameter at /php/ajax.php. An attacker can inject malicious JavaScript code that gets stored and executed when other users access the affected content, potentially leading to session hijacking or credential theft.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Zbzcms installation and versionLocate the Zbzcms installation directory and check for version identifiers in source files such as index.php, about.php, or a dedicated version/config fileAffected if The installed version is Zbzcms 1.0
-
Verify ajax.php endpoint existsCheck for the presence of /php/ajax.php in the web root directoryAffected if The file /php/ajax.php exists in the web application
-
Identify if neirong parameter handling is enabledExamine the source code of /php/ajax.php to confirm it processes the neirong parameter and stores user inputAffected if The ajax.php script contains logic that accepts and processes the neirong parameter for storage
-
Check for user-generated content storage mechanismReview the application database schema or file storage to see if user-supplied content from the neirong field is persistedAffected if The application stores neirong parameter values for later display to users (stored XSS condition)
-
Determine if output encoding is appliedInspect the code paths where neirong content is rendered back to users - look for htmlspecialchars or equivalent encoding functionsAffected if The neirong content is rendered to users without proper encoding or sanitization
A user is affected if they are running Zbzcms v1.0 with the /php/ajax.php endpoint active and the neirong parameter functionality enabled, where user input is stored and displayed without sanitization.
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 dataImplement input validation and sanitization for the neirong parameter, apply context-aware output encoding when rendering user-supplied content, and consider implementing Content Security Policy (CSP) headers to mitigate XSS execution.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27125 — 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-27125 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