dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2024-48823

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Local file inclusion in Automatic Systems Maintenance SlimLane 29565_d74ecce0c1081d50546db573a499941b10799fb7 allows a remote attacker to escalate privileges via the PassageAutoServer.php page.

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 confidence

A Local File Inclusion (LFI) vulnerability in Automatic Systems Maintenance SlimLane's PassageAutoServer.php allows remote attackers to include arbitrary files from the server filesystem, potentially leading to privilege escalation through access to sensitive system files, configuration files, or authentication credentials.

MitigationImplement strict input validation with whitelist-based allowlists for file paths, disable directory traversal sequences, and ensure PHP configurations restrict file inclusion to expected directories only.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate SlimLane installation and PassageAutoServer.php
    Search the web server document root for SlimLane-related directories and the file PassageAutoServer.php. Common paths may include /var/www/html/, /web/, or application-specific directories. Use: find / -name 'PassageAutoServer.php' 2>/dev/null
    Affected if PassageAutoServer.php file exists on the server and is accessible via the web server
  2. Identify the file inclusion parameter
    Review the source code of PassageAutoServer.php and identify parameters that accept file paths (commonly 'file', 'page', 'path', 'include', or similar). Look for require(), require_once(), include(), or include_once() statements using unvalidated input.
    Affected if The script uses include/require with a parameter that can be controlled via HTTP request without sanitization
  3. Test for directory traversal vulnerability
    Attempt to access known system files via the suspected parameter using ../ sequences. For example: curl 'http://[target]/PassageAutoServer.php?param=../../../../etc/passwd'. Compare the response against a baseline request.
    Affected if The application returns contents of files outside the intended directory, confirming LFI is possible
  4. Check PHP configuration
    Review php.ini or runtime PHP settings for dangerous settings such as allow_url_include=1 (which would allow RFI as well) and verify open_basedir restrictions if configured. Create a PHP info page or check existing one: php -i or locate php.ini
    Affected if PHP is configured without proper open_basedir restrictions and the LFI parameter is exploitable
  5. Verify authentication is required
    Determine whether PassageAutoServer.php is accessible without authentication by attempting direct HTTP requests to the file from an unauthorized network location or anonymous context.
    Affected if PassageAutoServer.php is accessible without authentication and contains the vulnerable file inclusion code

If SlimLane PassageAutoServer.php exists and can be accessed without authentication, with a file inclusion parameter that accepts directory traversal sequences, the environment is affected by this CVE.

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 input validation with whitelist-based allowlists for file paths, disable directory traversal sequences, and ensure PHP configurations restrict file inclusion to expected directories only.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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