dbcve.org
Sanitization Management SystemApplication · Sanitization Management System Project

CVE-2022-3673

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, was found in SourceCodester Sanitization Management System 1.0. Affected is an unknown function of the file /php-sms/classes/Master.php. The manipulation of the argument message leads to cross site scripting. It is possible to launch the attack remotely. The identifier of this vulnerability is VDB-212016.

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 stored cross-site scripting (XSS) vulnerability exists in SourceCodester Sanitization Management System 1.0 within the /php-sms/classes/Master.php file. The message parameter is not properly sanitized, allowing remote attackers to inject malicious JavaScript that executes when other users view the affected content. This is a medium-severity (CVSS 6.1) vulnerability exploitable over the network without authentication.

MitigationImplement proper input validation and context-aware output encoding for the message parameter in Master.php. Additionally, deploy Content Security Policy (CSP) headers as a defense-in-depth measure against XSS attacks.

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. Locate the Sanitization Management System installation
    Search for the /php-sms/ directory or files matching Master.php in the web root. Common paths include /var/www/html/php-sms or C:\xampp\htdocs\php-sms. Use 'find / -name Master.php 2>/dev/null' on Linux or check common web directories.
    Affected if The application directory /php-sms/ exists on the server with the classes/Master.php file present.
  2. Verify the application version is 1.0
    Check for a version file, README, or any file containing 'version 1.0' or '1.0' within the /php-sms/ directory. Also check the page source of any system page for version identifiers.
    Affected if The installed version is exactly 1.0.
  3. Examine the Master.php file for the vulnerable message parameter handling
    Open /php-sms/classes/Master.php and search for code that processes a 'message' parameter, particularly in functions handling sanitation records, messages, or user input. Look for lack of htmlspecialchars or sanitization functions around the message field.
    Affected if The Master.php file contains code that accepts and processes a 'message' parameter without proper sanitization (no htmlspecialchars, strip_tags, or output encoding).
  4. Identify if the vulnerable input form is accessible
    Determine if the web interface exposes a form that submits to the vulnerable code path. Look for pages that call the affected function in Master.php, such as sanitation forms, message submission forms, or any user-accessible input that feeds into the message parameter.
    Affected if The application has an active web interface with forms or parameters that allow submission of data to the vulnerable message parameter in Master.php.

The environment is affected if Sanitization Management System version 1.0 is installed with the vulnerable Master.php file containing unsanitized message parameter handling and accessible through the web interface.

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 proper input validation and context-aware output encoding for the message parameter in Master.php. Additionally, deploy Content Security Policy (CSP) headers as a defense-in-depth measure against XSS attacks.

Fix this in Sanitization Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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