CVE-2026-29962
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 v5.3.3-7 contains a Local File Inclusion (LFI) vulnerability caused by improper control of user-supplied file paths. The endpoint /vendor/phpunit/phpunit.php processes user-controlled parameters that directly affect file access operations without adequate validation, sanitization, or path restriction. This allows a remote attacker to exploit Path Traversal techniques to read arbitrary files from the underlying operating system and application directories, leading to sensitive information disclosure.
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 v5.3.3-7 contains a Local File Inclusion vulnerability in the /vendor/phpunit/phpunit.php endpoint. The application fails to validate, sanitize, or restrict user-supplied parameters used in file path operations, enabling path traversal attacks that allow remote attackers to read arbitrary files from the operating system and application directories.
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 MailInspector versionLocate the installed MailInspector version by checking the application interface, installation directory, or version file (typically in the main application directory or help/about section)Affected if The installed version is exactly 5.3.3-7 (this specific version is affected; other versions may not be)
-
Verify phpunit.php file existsCheck for the presence of the file /vendor/phpunit/phpunit.php in the web root or application installation directoryAffected if The file exists in the web-accessible directory (the vulnerability requires this file to be present)
-
Check web accessibility of vendor endpointAttempt to access the URL path /vendor/phpunit/phpunit.php via HTTP/HTTPS request to see if the endpoint is reachableAffected if The endpoint is accessible over the network (the flaw can only be exploited if the path is web-reachable)
-
Test for path traversal capabilitySend a request to /vendor/phpunit/phpunit.php with a manipulated path parameter (e.g., ../../../etc/passwd or similar) and observe if the application returns file contents outside its intended directoryAffected if The application returns content from files outside the expected directory, confirming path traversal is possible
You are affected if you are running MailInspector version 5.3.3-7, the /vendor/phpunit/phpunit.php file exists and is web-accessible, and the application allows path traversal via unsanitized parameters.
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 and path sanitization for all user-supplied file path parameters, ensuring paths are normalized and validated against an allowed whitelist of directories. Disable or remove the PHPUnit PHP script from production if not required.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-29962 — 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-29962 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