dbcve.org
Cups EasyApplication · Ajaysharma

CVE-2024-23872

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/locationmodify.php, in the description 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

Cups Easy 1.0 contains a stored Cross-Site Scripting (XSS) vulnerability in /cupseasylive/locationmodify.php via the description parameter. User-controlled input is not properly encoded before storage or output, allowing injection of malicious JavaScript that executes in authenticated users' browsers to steal session cookie credentials.

MitigationImplement input validation and proper output encoding on the description parameter in locationmodify.php, including context-aware escaping before any output to HTML. Additionally, configure Content Security Policy (CSP) headers to mitigate XSS exploitation.

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. Identify if Cups Easy 1.0 is installed
    Locate the web root directory and check for the presence of the 'cupseasylive' folder, or search for the file locationmodify.php in the web application directory structure.
    Affected if The cupseasylive directory with locationmodify.php exists in the web root.
  2. Confirm the exact product version
    Check version information in the application header, footer, or an admin/about page for 'Cups Easy' version 1.0.
    Affected if The installed version is Cups Easy 1.0 exactly.
  3. Verify the locationmodify.php endpoint is accessible
    Attempt to access /cupseasylive/locationmodify.php via HTTP or HTTPS request to confirm the file is served by the web server.
    Affected if The endpoint returns a valid HTTP response rather than a 404 error.
  4. Check if authentication is enabled
    Review session management configuration or attempt to access the endpoint without credentials to determine if authentication is required.
    Affected if The application requires authentication to access locationmodify.php.
  5. Inspect for existing XSS payloads in stored data
    If you have database access, query the locations or related table for the description field and examine its contents for suspicious script tags, event handlers, or encoded payloads. Alternatively, log into the application and view any location entries to see if unsanitized JavaScript executes in the browser.
    Affected if The description field contains unescaped HTML/script content that renders in the browser.

A user is affected if Cups Easy 1.0 is installed with the locationmodify.php endpoint accessible and the description parameter contains unsanitized input that gets stored and rendered without encoding.

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 proper output encoding on the description parameter in locationmodify.php, including context-aware escaping before any output to HTML. Additionally, configure Content Security Policy (CSP) headers to mitigate XSS exploitation.

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-23872 — 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-23872 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