CVE-2024-11021
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 · uneditedWebopac from Grand Vice info has Stored Cross-site Scripting vulnerability. Remote attackers with regular privileges can inject arbitrary JavaScript code into the server. When users visit the compromised page, the code is automatically executed in their browser.
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 confidenceStored Cross-site Scripting (XSS) vulnerability in Webopac from Grand Vice info allows authenticated users with regular privileges to inject malicious JavaScript into server-side data fields. The injected payload persists in the database and executes automatically in the browsers of any user who views the compromised content.
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>= 6, < 6.5.1>= 7, < 7.2.3CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 installed Webopac versionAccess the Webopac administration panel or check the software inventory for the Vice Webopac version numberAffected if The installed version falls within >= 6, < 6.5.1 or >= 7, < 7.2.3
-
Verify authentication configurationCheck if regular (non-admin) user accounts are enabled and can access data entry fields in the cataloging or patron management modulesAffected if Regular authenticated users have write access to server-side data fields that accept user-supplied content
-
Inspect database for suspicious contentQuery the database tables that store user-editable fields (such as bibliographic records, patron notes, or custom fields) for patterns matching script tags, javascript: URIs, or event handler attributesAffected if Any records contain unsanitized HTML or script tags in user-modifiable fields that were not properly escaped upon display
-
Test output renderingCreate a test record with a benign XSS payload in a data field (such as <script>alert(1)</script>), then view that record as a different regular user account to confirm if the payload executesAffected if The payload executes and triggers a JavaScript alert in the browser when the record is viewed
You are affected if your Webopac version is 6.x below 6.5.1 or 7.x below 7.2.3 AND regular users can modify data fields that are rendered to other users without proper output encoding.
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.
dbcve · scoped6.5.17.2.3
Implement robust input validation and output encoding/sanitization on all user-supplied data fields server-side before storage and before rendering. Consider implementing Content Security Policy (CSP) headers as defense-in-depth.
6.5.1 for v6.x branches; 7.2.3 for v7.x branches
- Identify the current Webopac version in use (check admin console or system information page)
- If running version 6.x (>=6 and <6.5.1): Upgrade to version 6.5.1 or later
- If running version 7.x (>=7 and <7.2.3): Upgrade to version 7.2.3 or later
- Obtain the upgrade package from the vendor (Grand Vice info) through official channels
- Follow vendor-provided installation/upgrade instructions to apply the update
- After upgrade, verify the application functions correctly
- As a security best practice after addressing stored XSS, review and sanitize any user-submitted content in the database that may contain malicious scripts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11021 — 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-11021 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