CVE-2024-23894
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/stockissuancecreate.php, in the issuancedate 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 confidenceCups Easy (Purchase & Inventory) v1.0 contains a reflected XSS vulnerability in /cupseasylive/stockissuancecreate.php via the issuancedate parameter. User-supplied input is not properly encoded before being rendered in the response, allowing injection of malicious JavaScript to steal authenticated users' session cookies.
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 installationLocate the Cups Easy application directory and check for version indicators such as a version.php file, footer/header files containing '1.0', or the application's admin panel showing the versionAffected if The application is installed and identifies as version 1.0 (including any sub-versions)
-
Verify vulnerable endpoint existsCheck if the file /cupseasylive/stockissuancecreate.php exists in the web root directoryAffected if The file stockissuancecreate.php exists in the cupseasylive subdirectory
-
Identify accessible parameterAccess the stockissuancecreate.php page via HTTP request and locate the form field for 'issuancedate' or inspect the page source for an input with name='issuancedate'Affected if The issuancedate parameter is present in the form and accepts user input
-
Test for reflected XSS vulnerabilitySubmit a test payload such as <script>alert(1)</script> as the issuancedate parameter value and verify if the payload is reflected unencoded in the responseAffected if The submitted script tags or other HTML/JavaScript are rendered directly in the response without encoding or sanitization
-
Check session cookie protectionInspect HTTP response headers Set-Cookie for the session identifier and verify if HttpOnly and Secure flags are absentAffected if Session cookies lack HttpOnly flag, making them accessible to JavaScript and vulnerable to theft via XSS
You are affected if Cups Easy v1.0 is installed, the stockissuancecreate.php endpoint exists, and the issuancedate parameter reflects unencoded input in the response.
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 issuancedate parameter. Additionally, configure HttpOnly and Secure flags on session cookies to prevent credential theft via XSS.
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23894 — 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-23894 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