CVE-2026-29963
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 has a Path Traversal vulnerability due to improper validation of user-supplied input in the /tap/dw.php endpoint. The text parameter is used to construct file paths without adequate normalization or restriction to a safe base directory. A remote attacker can exploit this flaw to access arbitrary files on the underlying operating system, resulting in unauthorized disclosure of sensitive information.
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 path traversal vulnerability in the /tap/dw.php endpoint. The 'text' parameter accepts user input that is directly used to construct file paths without validation, normalization, or restriction to a safe base directory. An attacker can use directory traversal sequences (e.g., ../../) to access arbitrary files on the host system.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 HSC MailInspector installationLocate the MailInspector installation directory and identify the installed version by checking product documentation, about page, or version file. Common paths may include /opt/mailinspector, /usr/local/mailinspector, or the web server document root.Affected if The product is installed and version equals 5.3.3-7
-
Verify the vulnerable endpoint existsCheck if the file /tap/dw.php exists within the MailInspector web directory. This is typically found in the web application's document root or a subdirectory.Affected if The file /tap/dw.php exists in the deployed application
-
Confirm the text parameter is acceptedSend a GET or POST request to /tap/dw.php with the 'text' parameter. Inspect whether the application accepts this parameter without immediate rejection.Affected if The endpoint accepts a 'text' parameter in the request
-
Test for path traversal vulnerabilitySend a request to /tap/dw.php with the 'text' parameter set to a traversal sequence such as '../../../../etc/passwd' or '../../windows/win.ini' and observe if file contents are returned or the application attempts to access the path.Affected if The application returns file contents or responds differently based on traversal input, indicating unrestricted file access
-
Check access controls on the endpointReview the application's configuration, .htaccess rules, or web server configuration to determine if /tap/dw.php is protected by authentication, IP restrictions, or other access controls.Affected if The endpoint is accessible without authentication or is exposed to untrusted users
A user is affected if HSC MailInspector version 5.3.3-7 is installed, the /tap/dw.php endpoint exists, and the 'text' parameter accepts traversal sequences that allow reading arbitrary files outside the intended directory.
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 strict input validation using basename() and realpath() to ensure the requested path resolves within an allowed directory. Alternatively, maintain an explicit whitelist of permitted files or use filesystem APIs that inherently prevent traversal.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-29963 — 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-29963 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