InjectionWeakness · CWE-74

CVE-2026-9574

HIGH · 7.3 CVSS v3.1 Published 2026-05-26

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

82/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

A flaw has been found in itsourcecode Student Transcript Processing System 1.0. This vulnerability affects unknown code of the file /admin/modules/student/trans.php. Executing a manipulation of the argument studentId/cid can lead to sql injection. The attack can be launched remotely. The exploit has been published and may be used.

Technical summary

dbcve analysis · moderate confidence

SQL injection vulnerability in itsourcecode Student Transcript Processing System 1.0 allows remote attackers to manipulate the studentId/cid parameters in /admin/modules/student/trans.php to inject arbitrary SQL commands, potentially enabling unauthorized data access or modification of student records.

MitigationImplement parameterized queries (prepared statements) for all database operations involving user-supplied input, particularly the studentId and cid parameters. Apply input validation and least-privilege database accounts to limit the impact of any successful injection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Confirm Student Transcript Processing System is installed

Search the web root for files containing 'Student Transcript Processing System' or look for the trans.php file in the /admin/modules/student/ directory

Affected if The application directory contains /admin/modules/student/trans.php from itsourcecode Student Transcript Processing System 1.0
Verify the vulnerable trans.php file exists

Locate the file trans.php within the /admin/modules/student/ path in the web application directory

Affected if The file /admin/modules/student/trans.php exists in the web application
Check if the studentId or cid parameters are exposed

Review the trans.php source code or test the endpoint /admin/modules/student/trans.php with HTTP requests containing studentId or cid parameters

Affected if The trans.php script accepts and uses studentId or cid parameters in database queries without proper parameterization
Determine if the /admin/ interface is network-accessible

Attempt to access the /admin/modules/student/trans.php endpoint via HTTP from an authorized location or review network exposure settings

Affected if The /admin interface is accessible from the network without proper authentication restrictions
Confirm the application version is 1.0

Check version metadata in the application footer, README, or configuration files for 'version 1.0' or 'itsourcecode' branding

Affected if The installed version is itsourcecode Student Transcript Processing System 1.0

A user is affected if they have itsourcecode Student Transcript Processing System version 1.0 running with the /admin/modules/student/trans.php file accessible over the network and the studentId/cid parameters accepting user input without SQL parameterization.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Implement parameterized queries (prepared statements) for all database operations involving user-supplied input, particularly the studentId and cid parameters. Apply input validation and least-privilege database accounts to limit the impact of any successful injection.

Have this fixed Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing4.0 h
Review / QA2.0 h

18.0 hours of engineering $3,200

Get help mitigating

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 locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-9574 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9574 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-9574?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsA vendor remedy is published

Severity 7.3 High

Exploit likelihood EPSS, next 30 days 0.3%

Remediation

A high-priority fix

Have this fixed 18 hrs · Moderate

Typical engagement from $3,200

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-9574 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References