dbcve.org
Sanitization Management SystemApplication · Sanitization Management System Project

CVE-2022-3672

MEDIUM · 6.1 CVSS v3.1 Published 2022-10-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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, which was classified as problematic, has been found in SourceCodester Sanitization Management System 1.0. This issue affects some unknown processing of the file /php-sms/classes/SystemSettings.php. The manipulation of the argument name/shortname leads to cross site scripting. The attack may be initiated remotely. The associated identifier of this vulnerability is VDB-212015.

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 · moderate confidence

A reflected cross-site scripting (XSS) vulnerability in SourceCodester Sanitization Management System 1.0 allows remote attackers to inject malicious JavaScript through the name and shortname parameters in /php-sms/classes/SystemSettings.php. User-supplied input is reflected back without proper sanitization or output encoding.

MitigationImplement input validation and output encoding for the name and shortname parameters in SystemSettings.php. Apply context-appropriate escaping (HTML, URL, JavaScript) before reflecting data back to the browser.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 application version
    Locate the version identifier in the application (typically in a config file, README, or about page). For SourceCodester Sanitization Management System, check the source code for version metadata or the project documentation shipped with the application.
    Affected if The installed version is exactly 1.0 (Sanitization Management System Project)
  2. Locate SystemSettings.php
    Navigate to the /php-sms/classes/ directory in the web root and verify the presence of the SystemSettings.php file.
    Affected if The file /php-sms/classes/SystemSettings.php exists in the deployed application
  3. Examine parameter handling for name and shortname
    Open SystemSettings.php and search for code that handles the 'name' and 'shortname' GET or POST parameters. Look for where these inputs are processed and reflected back to the user.
    Affected if The code processes 'name' or 'shortname' parameters and returns them to the browser without visible sanitization logic
  4. Check for output encoding functions
    Within SystemSettings.php, search for HTML escaping functions such as htmlspecialchars, htmlentities, or similar encoding functions applied to the name and shortname variables before output. Also check for any input validation routines.
    Affected if No htmlspecialchars, htmlentities, or equivalent sanitization functions are found applied to name/shortname before they are echoed or printed back to the user
  5. Verify the vulnerable code path is reachable
    Determine if the application exposes the affected functionality through a web-accessible endpoint. Check if the SystemSettings page or its processing logic is reachable via HTTP requests.
    Affected if The SystemSettings functionality that processes name/shortname parameters is accessible via the web application (not restricted by authentication or network controls)

A user is affected if they are running Sanitization Management System version 1.0, the SystemSettings.php file exists, and the name/shortname parameters are processed and reflected without sanitization or output encoding functions present in the code path.

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 input validation and output encoding for the name and shortname parameters in SystemSettings.php. Apply context-appropriate escaping (HTML, URL, JavaScript) before reflecting data back to the browser.

Fix this in Sanitization Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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