CVE-2026-30761
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 arbitrary file upload vulnerability in the pages/admin.uploadmapimg.php component of SourceBans Material Admin v1.1.6 allows attackers to execute arbitrary code via uploading a crafted image file.
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 confidenceAn arbitrary file upload vulnerability exists in the pages/admin.uploadmapimg.php component of SourceBans Material Admin v1.6. The application fails to properly validate uploaded files, allowing attackers to upload malicious PHP code disguised as image files and achieve remote code execution on the server.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 if SourceBans Material Admin v1.6 is installedLocate the SourceBans installation directory and check version information in the source code, typically found in a version.php file or the main index page.Affected if The application is SourceBans Material Admin version 1.6
-
Locate the admin.uploadmapimg.php fileSearch for the file pages/admin.uploadmapimg.php within the SourceBans installation directory.Affected if The file exists and is accessible within the web application
-
Verify if the upload directory permits script executionCheck the web server configuration and the upload directory .htaccess or equivalent settings. Look for AllowOverride None or script execution permissions in the designated upload folder.Affected if The upload directory allows PHP or script execution (no restrictions in place)
-
Inspect the file upload validation logicExamine the contents of admin.uploadmapimg.php to determine if it performs MIME type validation, magic byte checks, or extension whitelisting on uploaded files.Affected if The upload handler lacks proper validation (no MIME type check, no magic byte validation, or no extension whitelist)
A user is affected if they run SourceBans Material Admin v1.6 with the admin.uploadmapimg.php component accessible and the upload directory configured to allow script execution, combined with insufficient file validation in the upload handler.
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 server-side file validation including MIME type verification, magic byte checks, extension whitelisting (allow only safe image extensions), and store uploads outside the webroot or disable script execution in the upload directory.
- Consultation3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30761 — 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-30761 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