dbcve.org
InjectionWeakness · CWE-74

CVE-2026-10809

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A security flaw has been discovered in itsourcecode Fees Management System 1.0. This impacts an unknown function of the file /manage_user.php. The manipulation of the argument ID results in sql injection. The attack can be executed remotely. The exploit has been released to the public and may be used for attacks.

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 confidence

SQL injection vulnerability in itsourcecode Fees Management System 1.0 allows remote attackers to inject malicious SQL queries via the ID parameter in /manage_user.php. The application fails to properly sanitize user input before using it in database queries, enabling attackers to manipulate SQL statements and potentially exfiltrate, modify, or delete database contents.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in manage_user.php, implement strict input validation on all user-supplied parameters, and apply principle of least privilege to database accounts.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Confirm the application is itsourcecode Fees Management System
    Inspect the application banner, title, or check for identifiers indicating this specific system. Look for 'Fees Management System' branding in the web interface or source code comments.
    Affected if The application is itsourcecode Fees Management System version 1.0
  2. Locate the affected PHP file
    Check if the file /manage_user.php exists in the webroot of the deployed application. This file handles user management functionality.
    Affected if The file /manage_user.php is present in the application directory
  3. Verify the ID parameter is used in SQL queries
    Inspect the source code of /manage_user.php and locate any SQL queries that incorporate the 'ID' parameter from GET or POST requests. Search for patterns like $_GET['ID'] or $_POST['ID'] being concatenated into SQL strings.
    Affected if The code directly uses the 'ID' parameter in SQL queries without visible sanitization functions or prepared statements
  4. Check for absence of prepared statements
    Review the SQL query handling code in /manage_user.php for use of mysqli_prepare, PDO::prepare, or similar parameterized query functions. Look for evidence that queries are built by string concatenation with user input.
    Affected if SQL queries are constructed by concatenating the ID parameter directly into the query string rather than using parameterized queries
  5. Test the ID parameter for SQL injection
    Send a crafted request to /manage_user.php with SQL metacharacters in the ID parameter (such as ID=1' OR '1'='1) and observe the response for SQL error messages or unexpected behavior indicating injection.
    Affected if The application returns SQL syntax errors, different content, or exhibits behavior indicating the input is being interpreted as SQL code

You are affected if you are running itsourcecode Fees Management System 1.0 and the file /manage_user.php handles the ID parameter using direct string concatenation in SQL queries without prepared statements.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements in manage_user.php, implement strict input validation on all user-supplied parameters, and apply principle of least privilege to database accounts.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10809 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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