dbcve.org
Expense Management SystemApplication · Expense Management System Project

CVE-2022-2688

CRITICAL · 9.8 CVSS v3.1 Published 2022-08-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 vulnerability was found in SourceCodester Expense Management System. It has been rated as critical. This issue affects the function fetch_report_credit of the file report.php of the component POST Parameter Handler. The manipulation of the argument from/to leads to sql injection. The attack may be initiated remotely. The associated identifier of this vulnerability is VDB-205811.

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 SourceCodester Expense Management System's report.php file. The fetch_report_credit function improperly handles the from/to POST parameters, allowing remote attackers to inject malicious SQL queries via unsanitized user input.

MitigationImplement prepared statements/parameterized queries for all database operations involving user input. Apply vendor patches immediately and restrict network access to the affected endpoint until remediated.

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
Expense Management SystemApplication
Affected:all versions

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
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 checks

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

  1. Locate the Expense Management System installation
    Search the web server document root for files named report.php or directories containing 'expense' and 'management' in the path. Common locations include /var/www/html/, /www/, or C:\inetpub\wwwroot\
    Affected if The application is installed and the report.php file exists in the web accessible directory
  2. Identify if the fetch_report_credit function exists
    Open the report.php file and search for the string 'function fetch_report_credit' to confirm the vulnerable function is present in the codebase
    Affected if The fetch_report_credit function is found within report.php
  3. Verify the from and to POST parameters are used
    In report.php, locate the fetch_report_credit function and inspect how $_POST['from'] and $_POST['to'] parameters are handled. Look for direct insertion into SQL queries without sanitization or prepared statements
    Affected if The from and to POST parameters are directly concatenated into SQL queries without escaping or parameterized binding
  4. Confirm the application accepts these inputs
    Check if the web application endpoint report.php processes POST requests and passes the from/to parameters to the database function. Review any form submissions or API calls that target this file
    Affected if The application accepts POST requests with from/to parameters and forwards them to the vulnerable function without input validation
  5. Check database error disclosure
    If possible, send a malformed SQL payload via the from or to parameter (e.g., from parameter set to a single quote) and observe if SQL error messages are returned in the response, indicating unsanitized input handling
    Affected if SQL syntax errors are returned in the application response, confirming the injection point is exploitable

If the Expense Management System is installed with report.php containing the fetch_report_credit function that processes from/to POST parameters without sanitization, the environment is affected by this SQL injection vulnerability.

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

Implement prepared statements/parameterized queries for all database operations involving user input. Apply vendor patches immediately and restrict network access to the affected endpoint until remediated.

Fix this in Expense Management System 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-2022-2688 — 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-2022-2688 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