CVE-2026-30760
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 SourceBans Material Admin before v.1.1.6 (3ecd95e) allows attackers to manipulate arbitrary user data in the web app via a crafted XAJAX call.
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 confidenceThis is a cross-site scripting (XSS) vulnerability in SourceBans Material Admin's XAJAX request handling. Attackers can inject malicious scripts or manipulate arbitrary user data through crafted XAJAX calls by exploiting insufficient input validation on XAJAX endpoints.
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.
-
Locate SourceBans Material Admin installationSearch for files matching 'sourcebans' in your web directory, typically under /var/www, /home, or C:\inetpub. Look for directories containing 'sourcebans' or 'material-admin' and a file named 'version.php' or 'info.php'.Affected if SourceBans Material Admin is not found in the expected directories, indicating it may not be installed.
-
Identify installed versionOpen the version file (commonly version.php, info.php, or similar in the root/admin directory). Read the defined version constant or variable. Alternatively, check git log if the installation uses version control: run 'git log --oneline -1' to see the latest commit hash.Affected if The version is earlier than 1.1.6 or the commit hash precedes 3ecd95e.
-
Confirm XAJAX module is enabledSearch for XAJAX configuration in the SourceBans configuration files (often config.php, settings.php, or similar). Look for directives enabling xajax, ajax, or similar features. Also search for files containing 'xajax' in the codebase: run 'find . -iname "*xajax*"' or search for 'xajax' in PHP files.Affected if XAJAX functionality is present and enabled in the configuration.
-
Inspect XAJAX request handlers for input validationExamine PHP files in the xajax or ajax handler directories. Look for functions processing user input (GET/POST parameters) without proper sanitization. Search for patterns like $_GET, $_POST being used directly in output or database queries without sanitization functions such as htmlspecialchars, strip_tags, or parameterized queries.Affected if XAJAX handlers accept user input without sanitization routines present in the code.
The environment is affected if SourceBans Material Admin is installed with a version earlier than 1.1.6 (or commit before 3ecd95e) and XAJAX request handling is enabled with insufficient input validation present in the handler code.
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 dataUpgrade to SourceBans Material Admin v1.1.6 or later (commit 3ecd95e). If immediate upgrade is not possible, implement input sanitization and validation on all XAJAX request handlers to prevent injection of malicious content.
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30760 — 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-30760 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