CVE-2024-23892
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 · uneditedA 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/costcentercreate.php, in the costcenterid 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 confidenceA reflected Cross-Site Scripting (XSS) vulnerability exists in Cups Easy Purchase & Inventory v1.0 within the costcenterid parameter at /cupseasylive/costcentercreate.php. User-supplied input to this parameter is not properly encoded before being reflected in the response, allowing injection of malicious JavaScript that executes in the context of an authenticated user's 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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Cups Easy Purchase & Inventory is installedCheck if the web application directory contains the /cupseasylive/ path, typically found in the web server root (e.g., /var/www/html/cupseasylive/ or C:\inetpub\wwwroot\cupseasylive\).Affected if The /cupseasylive/ directory exists on the server.
-
Verify the application versionLocate any version file, README, or about page within the Cups Easy installation. Common paths include version.php, readme.txt, or an admin panel 'About' section. Compare the installed version to 1.0.Affected if The installed version is exactly 1.0.
-
Confirm the vulnerable script existsCheck for the existence of /cupseasylive/costcentercreate.php on the web server.Affected if The file costcentercreate.php exists in the /cupseasylive/ directory.
-
Test for XSS in the costcenterid parameterWith an authenticated session, submit a test payload such as <script>alert(1)</script> to the costcenterid parameter at /cupseasylive/costcentercreate.php (via GET or POST). Examine the HTTP response to see if the payload is reflected unescaped in the HTML output.Affected if The costcenterid parameter reflects the raw input without HTML encoding in the response.
If Cups Easy Purchase & Inventory v1.0 is installed, the costcentercreate.php file exists, and the costcenterid parameter reflects unencoded input, the environment is vulnerable to CVE-2024-23892.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper input validation and output encoding for the costcenterid parameter, using context-aware escaping functions (e.g., htmlspecialchars with appropriate encoding) before reflecting user input in HTML output.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23892 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-23892 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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