dbcve.org
Sanitization Management SystemApplication · Sanitization Management System Project

CVE-2022-3868

CRITICAL · 9.8 CVSS v3.1 Published 2022-11-05
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 classified as critical has been found in SourceCodester Sanitization Management System. Affected is an unknown function of the file /php-sms/classes/Master.php?f=save_quote. The manipulation of the argument id leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-213012.

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

A critical SQL injection vulnerability exists in SourceCodester Sanitization Management System at /php-sms/classes/Master.php?f=save_quote where the 'id' parameter is not properly sanitized before being used in SQL queries. This allows remote attackers to inject arbitrary SQL commands, potentially leading to unauthorized database access, data exfiltration, or complete system compromise.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements for all user inputs, particularly the 'id' parameter in the save_quote function, and implement input validation. 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.

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
Sanitization Management SystemApplication
Affected:= 1.0

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. Identify the installed application version
    Locate any version file or header in the Sanitization Management System web root (check for version.php, README, or admin panel About section). Compare the version to 1.0.
    Affected if The application is SourceCodester Sanitization Management System version 1.0
  2. Locate the vulnerable script file
    Check if the file /php-sms/classes/Master.php exists in the web document root.
    Affected if The file Master.php exists at the path /php-sms/classes/
  3. Inspect the save_quote function for dynamic SQL
    Open Master.php and locate the save_quote function. Search for SQL query statements (SELECT, INSERT, UPDATE, DELETE) that use the 'id' parameter directly in the query string without escaping or parameter binding.
    Affected if The save_quote function contains SQL queries that incorporate the 'id' parameter without prepared statements or sanitization functions
  4. Verify the id parameter reaches the SQL query unsanitized
    Trace the code flow from where $_POST['id'] or $_GET['id'] is received to where it is inserted into the SQL query. Confirm no escaping function (mysqli_escape_string, addslashes, etc.) or parameter binding (bind_param) is applied.
    Affected if The 'id' parameter is used directly in SQL queries without escaping, binding, or validation
  5. Confirm network accessibility of the affected endpoint
    Verify the web application is accessible over the network and the endpoint /php-sms/classes/Master.php?f=save_quote is reachable (check if the application is deployed and not behind proper network restrictions).
    Affected if The application is deployed and accessible to network attackers who can send requests to the save_quote endpoint

You are affected if you are running Sanitization Management System version 1.0 with the Master.php file present and the save_quote function uses the id parameter in unsanitized dynamic SQL queries.

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 for all user inputs, particularly the 'id' parameter in the save_quote function, and implement input validation. Apply principle of least privilege to database accounts.

Fix this in Sanitization Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3868 — 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-3868 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