CVE-2026-33273
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 · uneditedUnrestricted upload of file with dangerous type issue exists in MATCHA INVOICE 2.6.6 and earlier. If this vulnerability is exploited, an arbitrary file may be created by an administrator of the product. As a result, arbitrary code may be executed on the server.
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 · moderate confidenceUnrestricted file upload vulnerability in MATCHA INVOICE versions 2.6.6 and earlier allows authenticated administrators to upload files without proper validation of file types. This enables uploading of dangerous file types (e.g., PHP shells, executable files) that can be used to achieve arbitrary code execution on the server.
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<= 2.6.6CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 installed MATCHA INVOICE versionAccess the administrative interface or check the application files for a version indicator (typically found in an about page, configuration file, or software metadata)Affected if The displayed version number is 2.6.6 or lower
-
Locate the file upload functionalityNavigate to the administrator control panel and identify any modules or pages that handle file uploads (e.g., logo upload, document attachment, invoice attachment features)Affected if An administrator-accessible file upload feature exists in the application
-
Verify file type validation is implementedInspect the application's upload handling code or configuration to determine if file type validation exists; attempt to upload a file with a non-standard extension (such as .php, .exe, or .phtml) through the upload featureAffected if The application accepts and stores files without validating the file type or content, or if uploaded files are accessible via web request
-
Check upload directory placementExamine the web server configuration and application settings to determine where uploaded files are stored relative to the webrootAffected if Uploaded files are stored within the web-accessible directory tree and can be executed or retrieved via HTTP requests
A user is affected if running MATCHA INVOICE version 2.6.6 or earlier with an accessible administrator file upload feature that lacks proper file type and content validation.
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 allowlist-based file type validation (checking both file extension AND content/MIME type), store uploads outside webroot, and disable script execution in the upload directory. Verify all file upload functionality across the application.
- Consultation3.0 h
- Implementation8.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33273 — 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-33273 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