dbcve.org
Cups EasyApplication · Ajaysharma

CVE-2024-23861

MEDIUM · 6.1 CVSS v3.1 Published 2024-01-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 has been reported in Cups Easy (Purchase & Inventory), version 1.0, whereby user-controlled inputs are not sufficiently encoded, resulting in a Cross-Site Scripting (XSS) vulnerability via /cupseasylive/unitofmeasurementcreate.php, in the unitofmeasurementid parameter. Exploitation of this vulnerability could allow a remote attacker to send a specially crafted URL to an authenticated user and steal their session cookie credentials.

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 reflected Cross-Site Scripting (XSS) vulnerability exists in Cups Easy Purchase & Inventory v1.0 within the /cupseasylive/unitofmeasurementcreate.php endpoint. The unitofmeasurementid parameter accepts user-controlled input without proper encoding, allowing injection of malicious scripts. When a victim clicks a specially crafted URL, the attacker's script executes in their browser, exfiltrating session cookie credentials.

MitigationApply output encoding to the unitofmeasurementid parameter before rendering it in HTML context, implement input validation allowing only expected characters, and consider adding Content-Security-Policy headers to mitigate XSS 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
Cups EasyApplication
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. Confirm Cups Easy Purchase & Inventory is installed
    Locate the application web root directory and check for the presence of cupseasylive folder, typically found in web server document roots (e.g., /var/www/html/, /htdocs/, C:\inetpub\wwwroot\)
    Affected if The cupseasylive directory exists on the server
  2. Verify the application version is 1.0
    Check for version files, README files, or common version indicators within the cupseasylive installation directory. Look for version.php, version.txt, or check any admin/about page for version information
    Affected if The installed version is Ajaysharma Cups Easy = 1.0
  3. Confirm the vulnerable endpoint exists
    Verify the file /cupseasylive/unitofmeasurementcreate.php exists in the web root. This can be done via file system inspection or by attempting to access the URL (e.g., https://yourserver/cupseasylive/unitofmeasurementcreate.php)
    Affected if The unitofmeasurementcreate.php file exists and is accessible via web
  4. Inspect parameter handling in unitofmeasurementcreate.php
    Review the source code of unitofmeasurementcreate.php to see how the unitofmeasurementid parameter is processed. Look for whether $_GET or $_REQUEST is used to capture this parameter and whether htmlspecialchars(), htmlentities(), or similar encoding functions are applied before output
    Affected if The unitofmeasurementid parameter is output without encoding (e.g., no htmlspecialchars with ENT_QUOTES)
  5. Test for reflected XSS manually
    Send a crafted request with a test payload in the unitofmeasurementid parameter (e.g., ?unitofmeasurementid=<script>alert(1)</script>) and examine if the script tag is reflected verbatim in the response HTML without encoding
    Affected if The payload is reflected unescaped in the HTML response

If Cups Easy v1.0 is installed and the unitofmeasurementcreate.php endpoint reflects the unitofmeasurementid parameter without proper HTML encoding, the environment is affected by this XSS 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

Apply output encoding to the unitofmeasurementid parameter before rendering it in HTML context, implement input validation allowing only expected characters, and consider adding Content-Security-Policy headers to mitigate XSS execution.

Fix this in Cups Easy 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-2024-23861 — 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-2024-23861 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