CVE-2026-10236
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 · uneditedA vulnerability has been found in SourceCodester Water Billing Management System 1.0. This issue affects some unknown processing of the file /classes/Users.php?f=save of the component User Management Endpoint. Such manipulation leads to improper authorization. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.
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 Water Billing Management System 1.0 has an improper authorization vulnerability in the User Management Endpoint at /classes/Users.php?f=save. This allows remote attackers to bypass authorization checks when saving user data, likely enabling unauthorized user creation or privilege escalation.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 the Water Billing Management System installationSearch your web server's document root for directories containing 'water billing' or 'billing' with files like Users.php, Master.php, or typical billing system structures. Check for a folder named 'water_billing' or similar.Affected if The application is installed on your server and accessible via web.
-
Identify the installed versionLook for version information in the application. Check files like README.md, README.txt, about.php, or any version.php file in the application root. Also inspect the main index.php or login page HTML for version strings.Affected if The installed version is 1.0 or you cannot confirm a version higher than 1.0.
-
Verify the vulnerable endpoint file existsCheck if the file /classes/Users.php exists in your installation. This file should be located in a 'classes' subdirectory within the application root.Affected if The file classes/Users.php exists in your installation.
-
Inspect the user save functionality for authorization controlsOpen /classes/Users.php and locate the 'save' function handler. Review the code to see if there are role-based access control (RBAC) checks, session validation, or permission checks before allowing user creation or modification.Affected if The save function lacks proper authorization checks (no role verification, no session user validation, or allows unauthenticated/anonymous access).
You are affected if you are running Water Billing Management System version 1.0 with the /classes/Users.php endpoint present and missing proper authorization controls on the save functionality.
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 role-based access control (RBAC) checks in the user save function to verify the requester has appropriate permissions before allowing user data modifications.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10236 — 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-10236 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