CVE-2023-36140
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 · uneditedIn PHPJabbers Cleaning Business Software 1.0, there is no encryption on user passwords allowing an attacker to gain access to all user accounts.
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 confidencePHPJabbers Cleaning Business Software 1.0 stores user passwords in plaintext without cryptographic hashing. An attacker who gains read access to the database or user records can obtain all credentials in cleartext and authenticate as any user.
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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed versionLocate the version file or admin panel in the PHPJabbers Cleaning Business Software installation. Check the software version displayed in the application or a version.php file within the installation directory.Affected if The installed version is exactly 1.0 (any installation of version 1.0 is affected)
-
Access the database user tableConnect to the MySQL database used by the application. Identify the table that stores user credentials (commonly named 'users', 'admin', or similar). Query the table to examine the password field contents.Affected if Password values appear as readable plaintext (e.g., 'mypassword123') rather than hashed strings (e.g., $2y$10$...)
-
Inspect password storage codeLocate PHP files that handle user registration or password updates. Search for SQL INSERT/UPDATE statements that store passwords. Examine whether password_hash(), password_verify(), or similar cryptographic functions are used.Affected if The code stores passwords directly into the database without applying any hashing function
-
Review authentication logicFind the login processing script. Examine how submitted passwords are compared against stored values - whether they are hashed before comparison or compared as plaintext.Affected if The authentication code compares the submitted password directly against plaintext database values
-
Check database schema for password column typeDescribe or inspect the user table structure. Note the data type and any constraints on the password column.Affected if The password column contains no indication of hashing (such as a fixed-length hash field or validation that values match hash format)
If the software version is 1.0 and passwords are stored in plaintext in the database rather than as hashed values, the environment is affected by this vulnerability.
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 strong password hashing (bcrypt/Argon2 via password_hash) for all stored passwords, create a migration script to hash existing plaintext passwords, and update authentication logic to use password_verify.
- Consultation2.0 h
- Implementation6.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36140 — 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-2023-36140 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