dbcve.org
Senayan Library Management SystemApplication · Slims

CVE-2023-3744

HIGH · 8.8 CVSS v3.1 Published 2023-10-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Server-Side Request Forgery vulnerability in SLims version 9.6.0. This vulnerability could allow an authenticated attacker to send requests to internal services or upload the contents of relevant files via the "scrape_image.php" file in the imageURL parameter.

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

Server-Side Request Forgery (SSRF) in SLims 9.6.0's scrape_image.php script via the imageURL parameter. An authenticated attacker can abuse this to make the server request internal resources or exfiltrate local file contents by providing internal URLs or file:// paths.

MitigationImplement strict allowlist-based input validation on the imageURL parameter to restrict requests to legitimate external sources only; consider network segmentation to limit server outbound access; apply any vendor patch if available.

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
Senayan Library Management SystemApplication
Affected:= 9.6.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Confirm SLims installation and version
    Locate the SLims installation and identify the installed version number. Check version files, admin panel 'About' page, or system information page for the exact version string.
    Affected if The installed version is exactly 9.6.0 (no patch applied)
  2. Locate the vulnerable scrape_image.php script
    Search the web root directory for the file scrape_image.php. This is the script containing the vulnerable imageURL parameter.
    Affected if The file scrape_image.php exists in the web-accessible directory
  3. Verify authentication requirement for the vulnerable endpoint
    Attempt to access scrape_image.php directly without credentials, or review the script's authentication mechanism to confirm whether unauthenticated access is possible.
    Affected if The script can be accessed without authentication or with valid user credentials (any privilege level)
  4. Inspect imageURL parameter handling in the script
    Examine the source code of scrape_image.php to determine whether the imageURL parameter is validated before use. Look for URL validation, allowlist enforcement, or lack thereof.
    Affected if The imageURL parameter is processed without proper validation of the URL scheme or destination
  5. Test for SSRF via internal resource access
    With valid credentials, send a request to scrape_image.php with imageURL pointing to an internal service (e.g., http://127.0.0.1, http://localhost) or file:// path to confirm the server fetches and processes the resource.
    Affected if The server successfully retrieves and processes internal URLs or local file contents via the imageURL parameter

You are affected if SLims version 9.6.0 is installed, the scrape_image.php script exists, and the imageURL parameter can be abused to make the server fetch internal resources or local files without proper validation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict allowlist-based input validation on the imageURL parameter to restrict requests to legitimate external sources only; consider network segmentation to limit server outbound access; apply any vendor patch if available.

Fix this in Senayan Library Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-3744 — 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-2023-3744 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