CVE-2026-34184
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 · uneditedAlanWeb SCADA does not enforce authorization for some directories. This allows an unauthorized attacker to read all files in these directories and even execute some of them. Critically the attacker could run PHP scripts directly on the connected database. This issue was fixed in AlanWeb SCADA version 9.8.5
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 confidenceThe Hydrosystem Control System fails to enforce authorization checks on certain directories, allowing unauthenticated attackers to read all files within those directories and execute executable files. The most severe impact is the ability to run PHP scripts directly on the connected database server, enabling complete system compromise through remote code execution.
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< 9.8.5CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 the Hydrosystem Control System installation and versionLocate the main application files and check the version information typically found in the system configuration, about page, or version file. Common locations include the web root directory or the application's manifest file.Affected if The installed version is Hydrosystem.poznan Control System and the version is below 9.8.5
-
Verify if the system exposes web-accessible directoriesReview the web server configuration and the application's directory structure to identify which directories are accessible via HTTP/HTTPS without authentication. Check for directories that should require authorization but may be publicly accessible.Affected if Directories that should be protected by authorization checks are accessible without authentication
-
Check if PHP execution is enabled in accessible directoriesExamine the web server configuration (such as .htaccess files, Apache vhost settings, or IIS handler mappings) to determine if PHP scripts can be executed in directories that are accessible to unauthenticated users.Affected if PHP execution is permitted in directories accessible without authentication, allowing attackers to run arbitrary PHP code
-
Test for unauthenticated file read accessAttempt to access files in the unprotected directories using a web browser or HTTP client without providing credentials. Start with non-sensitive files to confirm the directory is accessible, then verify if sensitive files can be read.Affected if Files within protected directories can be read without any authentication being required
The environment is affected if Hydrosystem.poznan Control System version below 9.8.5 is running and unauthenticated access to certain directories or PHP execution in those directories is possible.
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 · scoped9.8.5
Upgrade to Hydrosystem Control System version 9.8.5 or later to remediate this vulnerability. As an interim measure, restrict network access to the system and disable PHP execution in accessible directories.
Hydrosystem Control System version 9.8.5
- 1. Create a complete backup of the current Hydrosystem Control System installation, including all configuration files and databases
- 2. Download Hydrosystem Control System version 9.8.5 from the official vendor source (www.hydrosystem.poznan.pl)
- 3. Review the vendor's upgrade documentation for version 9.8.5
- 4. Apply the upgrade to your Control System installation following the vendor's recommended procedure
- 5. After upgrading, verify that authorization is now properly enforced for all directories
- 6. Confirm that PHP scripts can no longer be executed without proper authentication
- 7. Test that the database connection works correctly with the updated version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34184 — 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-34184 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