CVE-2018-18587
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 · uneditedBigProf AppGini 5.70 stores the passwords in the database using the MD5 hash.
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 confidenceBigProf AppGini 5.70 stores user passwords in the database using the MD5 hashing algorithm, which is cryptographically weak and vulnerable to brute-force and rainbow table attacks. MD5 is considered obsolete for password storage due to its speed and known cryptographic weaknesses.
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= 5.70CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify AppGini versionLocate the AppGini installation directory and check the version file or footer/header in the application. Look for version information in the main configuration files or the application's login page source.Affected if The installed version is exactly 5.70
-
Examine password storage in databaseQuery the users table in the database (commonly named 'appgini_users' or similar) to inspect the password field. Retrieve a sample password hash and analyze its format.Affected if Password hashes appear as 32-character hexadecimal strings (characteristic of MD5) rather than longer hashes with salting (e.g., bcrypt, Argon2)
-
Check application code for hashing functionExamine the application source files related to authentication, typically in a 'hooks' or 'security' directory. Look for the password hashing implementation, searching for 'md5', 'hash', or 'password' function calls.Affected if The code uses PHP's md5() function or similar for password hashing instead of password_hash() or other modern algorithms
-
Verify password salt usageInspect whether passwords are stored with a unique salt per user. Check the database schema for a separate salt field or examine if the hash format includes embedded salt.Affected if No per-user salt is used, meaning identical passwords produce identical hashes (making rainbow table attacks possible)
The environment is affected if BigProf AppGini version 5.70 is running and user passwords in the database are stored as unsalted 32-character MD5 hashes.
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 dataReplace MD5 with a modern password hashing algorithm such as bcrypt, Argon2, or PBKDF2, and migrate existing password hashes to the new format.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-18587 — 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-2018-18587 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