CVE-2026-30996
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 · uneditedAn issue in the file handling logic of the component download.php of SAC-NFe v2.0.02 allows attackers to execute a directory traversal and read arbitrary files from the system via a crafted GET request.
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 confidenceThe download.php component in SAC-NFe v2.0.02 contains a directory traversal vulnerability that allows remote attackers to read arbitrary files by using '../' sequences in a crafted GET request parameter to access files outside the intended download directory.
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
- 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.
-
Locate download.php componentSearch the web root for the file download.php (e.g., find /var/www -name 'download.php' 2>/dev/null or locate download.php)Affected if download.php from SAC-NFe v2.0.02 is found on the system
-
Identify SAC-NFe versionCheck version files, about page, or metadata in SAC-NFe installation directory for version string '2.0.02'Affected if Installed version is 2.0.02 exactly, or falls within an unpatched range around 2.0.02
-
Verify parameter acceptanceInspect download.php source code to confirm it accepts a GET parameter (commonly 'file' or 'filename') for file retrievalAffected if The script accepts a file parameter without server-side validation
-
Check for directory traversal protectionReview download.php code for use of realpath() or similar path sanitization on the input parameter before file accessAffected if No realpath() validation or whitelist check is performed on the file parameter before fopen/readfile operations
-
Test traversal vulnerabilitySend a crafted GET request such as download.php?file=../../../../etc/passwd and observe if the file content is returned (local test only with authorization)Affected if The server returns file contents outside the intended download directory
A system is affected if SAC-NFe v2.0.02 is installed, download.php accepts a file parameter without realpath() validation, and directory traversal sequences are not blocked.
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 on the file parameter using realpath() to verify the resolved path stays within allowed directories, and restrict file access to a whitelist of permitted files.
- 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-30996 — 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-30996 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