CVE-2024-23885
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/countrymodify.php, in the countryid 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 confidenceThis is a reflected Cross-Site Scripting (XSS) vulnerability in Cups Easy Purchase & Inventory version 1.0. The countrymodify.php file does not properly sanitize or encode the countryid parameter, allowing injection of malicious JavaScript code. An authenticated user clicking a specially crafted URL would have their session cookies stolen by the attacker's executed JavaScript.
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.
-
Identify if Cups Easy Purchase & Inventory is installedLocate the web application directory and look for the main application files or check the application banner/version information served by the web server.Affected if Cups Easy Purchase & Inventory version 1.0 is present on the server
-
Verify the exact version of Cups EasyCheck the application's version file, about page, or any version metadata within the application root directory.Affected if The installed version is exactly 1.0 (any patch version within 1.0 branch)
-
Confirm countrymodify.php existsSearch the web document root for the file countrymodify.php or any country-related PHP files within the application.Affected if The file countrymodify.php exists in the application directory
-
Check if authentication is enabled for the applicationReview the application's login configuration or session management settings to determine if user authentication is required and active.Affected if User authentication is enabled and functional, meaning an attacker could potentially log in to exploit the XSS
-
Verify the countryid parameter is handled without sanitizationReview the source code of countrymodify.php and locate how the countryid parameter is processed and output in the page response.Affected if The countryid parameter is directly output in the HTTP response without proper encoding or sanitization
A user is affected if Cups Easy Purchase & Inventory version 1.0 is installed, countrymodify.php is present, and the application accepts authenticated users, allowing the countryid parameter to reflect unencoded input.
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 dataApply proper input validation and output encoding to the countryid parameter in countrymodify.php. Implement context-aware output encoding and consider adding Content-Security-Policy headers and httpOnly flags on session cookies to further reduce impact.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23885 — 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-23885 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