dbcve.org
Slims7 CendanaApplication · Slims

CVE-2017-7242

MEDIUM · 6.1 CVSS v3.0 Published 2017-03-23
Fix available
A fix is available. Upgrade to after 2017-03-23 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Multiple Cross-Site Scripting (XSS) were discovered in admin/modules components in SLiMS 7 Cendana through 2017-03-23: the keywords parameter to bibliography/checkout_item.php, bibliography/dl_print.php, bibliography/item.php, bibliography/item_barcode_generator.php, bibliography/printed_card.php, circulation/loan_rules.php, master_file/author.php, master_file/coll_type.php, and master_file/doc_language.php and the quickReturnID field to circulation/ajax_action.php.

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 confidence

Multiple reflected Cross-Site Scripting (XSS) vulnerabilities exist in SLiMS 7 Cendana admin/modules. The 'keywords' parameter in 9 bibliography and master_file PHP files (checkout_item.php, dl_print.php, item.php, item_barcode_generator.php, printed_card.php, loan_rules.php, author.php, coll_type.php, doc_language.php) and the 'quickReturnID' field in circulation/ajax_action.php do not properly sanitize user input before reflecting it in HTML output.

MitigationImplement proper input validation and output encoding/escaping for all user-supplied parameters in the affected files to prevent XSS attacks.

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
Slims7 CendanaApplication
Affected:<= 2017-03-23

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify SLiMS installation version
    Locate the version file or admin panel that displays the SLiMS version. Common locations include a version.php file in the root directory, or check the admin dashboard for the version information.
    Affected if The installed SLiMS version is Cendana (7) and the version date is on or before March 23, 2017.
  2. Locate vulnerable admin module files
    Search for the following PHP files in the admin/modules directory: checkout_item.php, dl_print.php, item.php, item_barcode_generator.php, printed_card.php, loan_rules.php, author.php, coll_type.php, doc_language.php.
    Affected if Any of these files exist in the admin/modules directory, indicating the affected component is present.
  3. Verify the keywords parameter handling
    Examine the source code of one of the affected bibliography or master_file PHP files (such as author.php or item.php) and locate where the 'keywords' parameter is handled and reflected in HTML output.
    Affected if The code shows the 'keywords' parameter being output directly to HTML without visible sanitization or encoding functions.
  4. Check circulation ajax_action.php for quickReturnID
    Locate and examine circulation/ajax_action.php and look for how the 'quickReturnID' parameter is processed and reflected in the response.
    Affected if The 'quickReturnID' parameter is reflected in the output without sanitization.
  5. Confirm admin access is available
    Verify that the web application admin interface is accessible, as the vulnerable files are located in the admin/modules path.
    Affected if Admin access to SLiMS is possible, allowing interaction with the vulnerable modules.

A system is affected if it runs SLiMS 7 Cendana version dated 2017-03-23 or earlier and has the admin interface accessible with vulnerable files present that reflect user input without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2017-03-23
Interim mitigation

Implement proper input validation and output encoding/escaping for all user-supplied parameters in the affected files to prevent XSS attacks.

Fix this in Slims7 Cendana Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing4.0 h
  • Review / QA2.0 h
22.0 hours of engineering $3,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-7242 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-7242 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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