CVE-2026-30994
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 · uneditedIncorrect access control in the config.php component of Slah v1.5.0 and below allows unauthenticated attackers to access sensitive information, including active session credentials.
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 confidenceSlah v1.5.0 and below contains an incorrect access control vulnerability in the config.php component. The component allows unauthenticated attackers to directly access config.php and retrieve sensitive information, including active session credentials, without any authentication or authorization checks.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Locate Slah installationSearch the web root for files named config.php or directories containing Slah application files (controllers, models, views folders, etc.)Affected if Slah is installed on the system
-
Determine installed Slah versionCheck version.php, composer.json, or any version file in the Slah installation directory; if unavailable, check the main index.php or a known changelog file for version markersAffected if Installed version is 1.5.0 or lower, or version cannot be determined and the file exists in an older installation
-
Verify config.php exists in web-accessible locationLocate config.php within the public web root (htdocs, public_html, or the main application directory served by the web server)Affected if config.php file exists in a web-accessible directory
-
Test unauthenticated access to config.phpUsing a browser or curl command, attempt to access the config.php file directly via HTTP (e.g., curl -s http://TARGET_URL/config.php) without providing any authentication tokens or session cookiesAffected if The file is served and returns HTTP 200 with content (not HTTP 403/401), indicating it is directly accessible without authentication
-
Check for sensitive data exposureIf config.php is accessible, inspect the response content for sensitive variables such as database credentials, API keys, session identifiers, or configuration arrays containing credentialsAffected if The response contains unencrypted credentials, session tokens, database connection strings, or other sensitive configuration data
A Slah installation version 1.5.0 or below with config.php present in a web-accessible directory and directly retrievable via HTTP without authentication indicates the environment is affected by CVE-2026-30994.
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 authentication and authorization checks on the config.php component to ensure only authenticated users with appropriate privileges can access sensitive configuration files. Consider moving config.php outside the web root or adding .htaccess/deny rules.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30994 — 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-2026-30994 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