CVE-2026-29965
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 · uneditedHSC MailInspector 5.3.3-7 is vulnerable to Cross Site Scripting (XSS) in the /police/WarningUrlPage.php endpoint due to improper neutralization of user-supplied input that uses alternate or obfuscated JavaScript syntax.
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 confidenceHSC MailInspector 5.3.3-7 contains a reflected XSS vulnerability in /police/WarningUrlPage.php where user-supplied input is not properly sanitized, allowing alternate or obfuscated JavaScript syntax to bypass existing filters and execute in the victim's browser.
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= 5.3.3-7CVSS 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.
-
Identify HSC MailInspector installationLocate the MailInspector installation directory and determine the installed version by examining version files, about pages, or the application banner displayed in the web interfaceAffected if Installed version is 5.3.3-7
-
Locate the vulnerable PHP fileSearch the MailInspector web root directory for the file /police/WarningUrlPage.php or WarningUrlPage.php within a /police/ subdirectoryAffected if The file WarningUrlPage.php exists in a /police/ path within the application
-
Verify web exposure of the affected endpointAttempt to access the /police/ path via HTTP/HTTPS from a browser or curl request (e.g., http://yourserver/police/WarningUrlPage.php)Affected if The /police/WarningUrlPage.php endpoint responds to HTTP requests and is reachable from the network
-
Test for reflected input vulnerabilitySend a request to WarningUrlPage.php with a test XSS payload in the query string (e.g., ?url=test) and examine whether the input is reflected in the response without proper encoding or sanitizationAffected if User-supplied parameters are reflected in the HTML response without being encoded or sanitized
You are affected if HSC MailInspector version 5.3.3-7 is installed, the /police/WarningUrlPage.php file exists, and user-supplied input in that file is reflected in the response without proper 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 robust input validation and output encoding that specifically accounts for obfuscated JavaScript syntax variants; consider using established sanitization libraries or a WAF as a defense-in-depth measure.
- Consultation4.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,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-29965 — 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-29965 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