dbcve.org
Php Point Of SaleApplication · Phppointofsale

CVE-2022-40289

CRITICAL · 9.0 CVSS v3.1 Published 2022-10-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable

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
The application was vulnerable to an authenticated Stored Cross-Site Scripting (XSS) in the upload and download functionality, which could be leveraged to escalate privileges or compromise any accounts they can coerce into observing the targeted files.

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

The application contains a stored cross-site scripting (XSS) vulnerability in its file upload and download mechanisms. An authenticated attacker can embed malicious JavaScript within uploaded files (e.g., in metadata, filename, or file content) that will execute when other users download or interact with those files, enabling session hijacking, privilege escalation, or account compromise.

MitigationImplement strict input validation and sanitization on file uploads, validate file types and content, and apply proper output encoding with Content-Disposition headers on downloads to prevent script execution.

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
Php Point Of SaleApplication
Affected:= 19.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
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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 Php Point of Sale version
    Locate the version file or admin panel about page - typically in application/config/config.php, version.php, or the admin dashboard under Help > About
    Affected if The installed version is exactly 19.0 (only this version is listed as affected)
  2. Confirm file upload functionality exists
    Navigate to the file upload feature in the application - typically found in items/import, sales/import, or inventory management sections where CSV, Excel, or image uploads are supported
    Affected if File upload functionality is accessible to authenticated users and accepts files that can contain metadata or content that could embed scripts
  3. Verify file download mechanism is present
    Check for file download/export features - look for download links for uploaded files, exports of inventory, sales reports, or receipt templates
    Affected if The application allows downloading previously uploaded files without proper Content-Disposition headers
  4. Inspect download response headers
    Use browser developer tools or curl to intercept a file download request and inspect the response headers, specifically looking for Content-Disposition: attachment; filename= pattern
    Affected if Content-Disposition header is missing or set to inline, or filename is not sanitized (allowing executable extensions or script-capable filenames)
  5. Check uploaded file metadata handling
    Upload a test file with non-printable characters or script tags in filename/metadata, then download it and observe if the application reflects unsanitized values in the download response
    Affected if The application returns the file with unsanitized metadata or filename in headers/body, allowing script execution

You are affected if you are running Php Point of Sale version 19.0 and have file upload/download features enabled for authenticated users without proper Content-Disposition headers and input sanitization.

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 strict input validation and sanitization on file uploads, validate file types and content, and apply proper output encoding with Content-Disposition headers on downloads to prevent script execution.

Fix this in Php Point Of Sale Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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