CVE-2026-3747
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 identified in itsourcecode University Management System 1.0. Affected by this issue is some unknown functionality of the file /add_result.php. Such manipulation of the argument subject leads to sql injection. The attack may be launched remotely. The exploit is publicly available and might be used.
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 subject parameter of /add_result.php in itsourcecode University Management System 1.0 allows remote attackers to inject malicious SQL queries. The lack of input sanitization or parameterized queries enables arbitrary database manipulation.
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 if the University Management System is installedSearch the web server document root for directories or files containing 'university' or 'ums' in the name. Look for the presence of add_result.php file.Affected if The application directory and add_result.php file are found on the server
-
Verify the application versionCheck the application for a version identifier in source files, README, or configuration. Common paths include version.php, about.php, or a config file in the application root.Affected if The installed version matches 1.0 of Angeljudesuarez University Management System
-
Confirm the vulnerable script existsLocate add_result.php in the web root and verify it contains SQL query logic that processes a 'subject' parameter from POST or GET requests.Affected if add_result.php exists and contains SQL queries that use the subject parameter without visible sanitization or prepared statements
-
Determine if the application is network-accessibleCheck network configuration to see if the web server hosting the application is accessible from untrusted networks or the public internet.Affected if The application is accessible from untrusted network locations, enabling remote exploitation
-
Check for input validation in the vulnerable codeReview add_result.php source code for use of mysqli_prepare, PDO prepared statements, or input sanitization functions like htmlspecialchars or filter_var on the subject parameter.Affected if The subject parameter is used directly in SQL queries without parameterization or sanitization
The environment is affected if Angeljudesuarez University Management System version 1.0 is installed with the add_result.php file accessible and the subject parameter used in unprotected SQL queries.
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 prepared statements/parameterized queries for all database operations in add_result.php, particularly for the subject parameter. Validate and sanitize all user inputs before using them in SQL queries.
- Consultation3.0 h
- Implementation4.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3747 — 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-3747 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