CVE-2026-3944
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 · uneditedA vulnerability was determined in itsourcecode University Management System 1.0. This vulnerability affects unknown code of the file /att_add.php. This manipulation of the argument Name causes sql injection. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized.
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 confidenceSQL injection vulnerability in the Name parameter of /att_add.php in itsourcecode University Management System 1.0. The lack of parameterized queries allows unauthenticated remote attackers to inject malicious SQL queries, potentially exfiltrating or manipulating the database. CVSS 9.8 indicates critical impact with low attack complexity.
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= 1.0CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 the University Management System versionLocate the application source files or check the application's 'about' or 'version' page. Look for version 1.0 specifically in the application documentation, footer, or installation files.Affected if The installed version is University Management System 1.0 (Angeljudesuarez/itsourcecode variant)
-
Locate the att_add.php fileSearch the web root directory for the file att_add.php. Common paths include /att_add.php or /includes/att_add.php. Use file system search: 'find . -name att_add.php' or check via HTTP request to the suspected path.Affected if The file att_add.php exists in the deployed application directory
-
Verify the Name parameter is acceptedSend an HTTP GET or POST request to att_add.php with a 'Name' parameter (e.g., ?Name=test or as form data). Check if the application processes this parameter without error or validation feedback.Affected if The att_add.php script accepts and processes a 'Name' parameter without immediate SQL error rejection
-
Confirm no input sanitization is presentExamine the att_add.php source code for SQL query handling. Look for direct insertion of the 'Name' parameter into SQL statements without parameterized queries, prepared statements, or escaping functions.Affected if The code shows direct string concatenation of the 'Name' parameter into SQL queries (e.g., 'INSERT INTO... VALUES(..., '$Name', ...)' without binding)
If the application is University Management System 1.0 and the att_add.php file exists and accepts a 'Name' parameter without parameterized queries, the environment is vulnerable to CVE-2026-3944.
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 dataReplace dynamic SQL queries in att_add.php with prepared statements/parameterized queries. Validate and sanitize all user inputs. Apply least-privilege database accounts. Deploy a WAF as a temporary compensating control until code fix is complete.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3944 — 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-3944 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