CVE-2024-24336
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 multiple Cross-site scripting (XSS) vulnerability in the '/members/moremember.pl', and ‘/members/members-home.pl’ endpoints within Koha Library Management System version 23.05.05 and earlier allows malicious staff users to carry out CSRF attacks, including unauthorized changes to usernames and passwords of users visiting the affected page, via the 'Circulation note' and ‘Patrons Restriction’ components.
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 · moderate confidenceMultiple stored XSS vulnerabilities in Koha LMS versions 23.05.05 and earlier in the '/members/moremember.pl' and '/members/members-home.pl' endpoints allow authenticated malicious staff users to inject malicious scripts via 'Circulation note' and 'Patrons Restriction' fields. When other staff users view these pages, the XSS payloads execute and perform CSRF attacks to modify usernames and passwords of victim users.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 Koha LMS installation and versionLocate the Koha installation directory and check the version file (typically in koha-conf.xml or a VERSION file in the root directory). Run: `grep -i version /path/to/koha/misc/koha_version` or check the admin interface version display.Affected if The installed version is 23.05.05 or any earlier version (e.g., 23.05.00 through 23.05.05).
-
Confirm vulnerable endpoints are accessibleVerify that the web server exposes /members/moremember.pl and /members/members-home.pl. Check the Apache/Nginx configuration for Koha and confirm these CGI scripts are accessible to staff users.Affected if These endpoints are accessible and the Koha staff client is enabled.
-
Check staff user access to member recordsLog in as a staff user with circulation privileges and confirm access to the 'Members' module. Navigate to a patron record to view the Circulation note and Patrons Restriction fields.Affected if Staff users can access member records where these fields are displayed.
-
Inspect Circulation note and Patrons Restriction fields for XSS payloadsQuery the database for stored XSS in these fields. Run: `SELECT borrowernumber, surname, circulation_note, restrictions FROM borrowers WHERE circulation_note LIKE '%<script%' OR restrictions LIKE '%<script%' OR other_xss_patterns;` Check these fields in the staff interface.Affected if Any stored XSS payloads (script tags, event handlers, or encoded JavaScript) exist in the Circulation note or Patrons Restriction fields.
A user is affected if they run Koha LMS version 23.05.05 or earlier and staff users have access to the vulnerable member management endpoints where malicious scripts could be injected into the Circulation note or Patrons Restriction fields.
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 output encoding for all user-supplied data displayed in these endpoints and add CSRF tokens to state-changing operations like username/password modifications.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24336 — 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-24336 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