CVE-2026-30252
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 · uneditedMultiple reflected cross-site scripting (XSS) vulnerabilities in the login.php endpoint of Interzen Consulting S.r.l ZenShare Suite v17.0 allows attackers to execute arbitrary Javascript in the context of the user's browser via a crafted URL injected into the codice_azienda and red_url parameters.
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 confidenceReflected cross-site scripting (XSS) vulnerabilities exist in the login.php endpoint of Interzen Consulting S.r.l ZenShare Suite v17.0. The codice_azienda and red_url parameters fail to properly sanitize user-supplied input, allowing injection of malicious JavaScript that executes in the context of the victim's browser when they visit a crafted URL.
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= 17.0= 17.0= 17.0= 17.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.
-
Verify installed ZenShare Suite versionLocate the application version information in the software (typically in an about page, admin panel, or version file within the web root) and confirm it is exactly version 17.0Affected if Installed version is 17.0 for any of these products: Interzen Zencrm, Interzen Zenhr, Interzen Zenproject, or Interzen Zenpurchase
-
Confirm login.php endpoint is accessibleAccess the login.php page via HTTP/HTTPS request (typically at /login.php or /?page=login within your ZenShare installation)Affected if login.php is accessible and returns a login page response
-
Test codice_azienda parameter for reflected XSSSubmit a crafted request to login.php with a test payload in the codice_azienda parameter (e.g., codice_azienda=<script>alert(1)</script>) and inspect the HTML response to see if the script tags are rendered unescapedAffected if The codice_azienda parameter value is reflected in the response without HTML encoding (script tags appear literally in the page source)
-
Test red_url parameter for reflected XSSSubmit a crafted request to login.php with a test payload in the red_url parameter (e.g., red_url=javascript:alert(1)) and inspect the HTML response to see if the payload is rendered without sanitizationAffected if The red_url parameter value is reflected in the response without proper encoding or validation
A user is affected if they are running ZenShare Suite version 17.0 and the login.php endpoint reflects the codice_azienda or red_url parameters back into the HTML without encoding, allowing injected script execution.
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 proper input validation and output encoding for the codice_azienda and red_url parameters in login.php. Additionally, configure the Content-Type header to 'text/html' with charset and consider implementing a Content Security Policy (CSP) to mitigate XSS execution.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30252 — 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-30252 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