dbcve.org
Wbce CmsApplication · Wbce

CVE-2025-67504

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 1.6.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 · unedited
WBCE CMS is a content management system. Versions 1.6.4 and below use function GenerateRandomPassword() to create passwords using PHP's rand(). rand() is not cryptographically secure, which allows password sequences to be predicted or brute-forced. This can lead to user account compromise or privilege escalation if these passwords are used for new accounts or password resets. The vulnerability is fixed in version 1.6.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 · high confidence

WBCE CMS versions 1.6.4 and below use PHP's non-cryptographically secure rand() function in GenerateRandomPassword() to create session passwords. An attacker can predict or brute-force these passwords, leading to user account compromise or privilege escalation via new account creation or password resets.

MitigationUpgrade to WBCE CMS version 1.6.5 or later which implements cryptographically secure password generation.

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
Wbce CmsApplication
Affected:< 1.6.5

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed WBCE CMS version
    Check the version file or admin dashboard. Typically, the version is displayed in the admin backend footer or can be found in a version.php or config file in the WBCE installation directory.
    Affected if Version is 1.6.4 or below (< 1.6.5)
  2. Locate the GenerateRandomPassword function
    Search the WBCE installation files for the function named 'GenerateRandomPassword'. This is typically in a helper, function, or tools file within the includes or admin directory.
    Affected if The function file exists in the installation
  3. Inspect the password generation logic
    Open the file containing GenerateRandomPassword() and examine the code inside the function to see what PHP function is used to generate random values.
    Affected if The function uses rand() instead of random_int(), random_bytes(), or openssl_random_pseudo_bytes()
  4. Verify session password generation is active
    Check if user registration, password reset, or session management features are enabled and functional on the site, as these would invoke the vulnerable GenerateRandomPassword() function.
    Affected if User account features that call the vulnerable function are in use

Affected if WBCE CMS version is below 1.6.5 and the GenerateRandomPassword() function uses the insecure rand() function for session password generation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.6.5 or later
Fixed in 1.6.5
Vendor patch github.com →
Interim mitigation

Upgrade to WBCE CMS version 1.6.5 or later which implements cryptographically secure password generation.

Recommended fix High confidence

1.6.5

  1. Backup the existing Wbce Cms installation and database before upgrading
  2. Upgrade Wbce Cms to version 1.6.5
  3. Verify that the GenerateRandomPassword() function no longer uses PHP's rand() function (it should now use a cryptographically secure random generator)
  4. Confirm the upgrade was successful by checking the CMS functionality

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wbce Cms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67504 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-67504 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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