CVE-2026-25355
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in skygroup Sanzo sanzo allows Stored XSS.This issue affects Sanzo: from n/a through < 2.4.3.
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 · moderate confidenceA stored XSS vulnerability in skygroup Sanzo allows attackers to inject malicious scripts into web pages through unsanitized user input. The malicious payload is stored in the application and executed when other users view the affected content, enabling session hijacking, credential theft, or defacement.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
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.
-
Identify the installed Sanzo versionLocate the application version information in the product's admin panel, about page, or version file (commonly found in config files, footer of web UI, or package metadata). Compare this version number to the fixed version 2.4.3.Affected if The installed version is lower than 2.4.3 (e.g., 2.4.2, 2.4.1, earlier releases).
-
Identify user input fields that store dataReview the application for features that accept and store user-provided data, such as user profiles, comments, messages, settings fields, or any form that saves input to a database for later display.Affected if The application stores user input in a database and retrieves it for display to other users.
-
Verify output encoding on stored contentSubmit a harmless test payload containing HTML or script tags (e.g., <script>alert(1)</script> or <img src=x onerror=alert(1)>) through a user input field. Then view the stored content as a different user or in a different context and inspect whether the tags render as plain text or execute as active code.Affected if The submitted HTML/script tags render as executable code (popup, error, or visible HTML elements) rather than being escaped or encoded as plain text.
-
Check application logs for XSS indicatorsReview application and web server logs for patterns indicating XSS attempts, such as script tags, event handlers (onerror, onload), or JavaScript URIs in request parameters that may have been stored and later triggered.Affected if Logs show successful storage and later retrieval of malicious script payloads that were not sanitized.
A user is affected if the installed Sanzo version is below 2.4.3 AND the application stores user input that is rendered without proper output encoding, allowing injected scripts to execute for other users.
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.
dbcve · scopedUpgrade to Sanzo version 2.4.3 or later to obtain the patch. Additionally, implement robust input validation and output encoding for all user-supplied data before rendering in HTML contexts.
2.4.3
- 1. Back up your current Sanzo installation and database before proceeding with any upgrade.
- 2. Review the official Sanzo release notes for version 2.4.3 to understand any required migration steps or configuration changes.
- 3. Download Sanzo version 2.4.3 or later from the official source.
- 4. Replace the existing Sanzo installation files with the new version, preserving any custom configurations.
- 5. Run any database migrations if required by the upgrade.
- 6. Verify the upgrade was successful and test that the application functions correctly.
- 7. Confirm the XSS vulnerability is resolved by verifying the fix in the updated code or release notes.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25355 — 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-2026-25355 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