CVE-2024-23867
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/statecreate.php, in the stateid 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 stored XSS vulnerability in Cups Easy Purchase & Inventory v1.0 in the stateid parameter of /cupseasylive/statecreate.php allows remote attackers to inject malicious JavaScript through insufficiently encoded user input, potentially leading to session hijacking via stolen cookies from authenticated users.
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 installationIdentify if the web application Cups Easy Purchase & Inventory v1.0 is running in your environment. Check running web services, installed applications, or review your software inventory for 'Ajaysharma Cups Easy' or 'Cups Easy' with version 1.0.Affected if The application is installed and accessible on your network
-
Verify the vulnerable endpoint existsLocate the file statecreate.php in your web root under the /cupseasylive/ directory path. Confirm the file exists and is accessible via HTTP/HTTPS.Affected if The file /cupseasylive/statecreate.php exists and is reachable
-
Check if stateid parameter is processedReview the statecreate.php source code and identify how the stateid parameter handles user input. Look for any input handling logic that processes the stateid field.Affected if The application processes user input through the stateid parameter without proper output encoding
-
Test for unencoded output reflectionSubmit a test payload (such as a benign HTML tag) to the stateid parameter via the statecreate.php form and inspect whether the value is reflected back in the response without HTML encoding.Affected if User input in stateid is reflected in responses without proper HTML encoding
-
Inspect session cookie security flagsExamine the session cookie configuration for the application. Check if the session cookie has HTTPOnly and Secure flags set. Inspect cookies returned by the application in browser dev tools or via curl.Affected if Session cookies lack HTTPOnly or Secure flags, making them vulnerable to theft via XSS
Your environment is affected if you are running Cups Easy Purchase & Inventory v1.0, the statecreate.php endpoint exists, and the stateid parameter reflects user input without proper encoding, allowing stored XSS that could steal session cookies lacking HTTPOnly/Secure protection.
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 input validation and output encoding for the stateid parameter, and set HTTPOnly and Secure flags on session cookies to prevent XSS-based session theft.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23867 — 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-23867 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