CVE-2025-67504·PHP vulnerability
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.
- Severity
- critical
- Software
- PHP
- Fixed in
- 1.6.5
- Published
- 2025-12-09
Affected versions
Until: 1.6.5
Fixed in: 1.6.5
How to fix this CVE
WBCE CMS versions 1.6.4 and earlier use a weak password generation function that relies on PHP's non-cryptographic rand() function, allowing attackers to predict generated passwords for new accounts or password resets. Upgrade WBCE CMS to version 1.6.5 or later, which replaces the vulnerable password generation logic with cryptographically secure alternatives. Immediately force password resets for all user accounts that may have been created or reset using the vulnerable function.
sudo dnf upgrade phpDefensia detects this vulnerability
How to check if you are affected
- Run `php -v` to confirm the installed PHP version and check if WBCE CMS is deployed on the system.
- Navigate to your WBCE CMS installation directory and check the version number in `version.php` or admin panel; versions 1.6.4 and below are vulnerable.
- Search your application logs for calls to GenerateRandomPassword() function: `grep -r 'GenerateRandomPassword' /path/to/wbce/cms/`
- Verify the patch by checking the WBCE CMS release notes and confirming version 1.6.5+ is installed: `cat /path/to/wbce/cms/version.php | grep VERSION`
FAQ
What is CVE-2025-67504?
This vulnerability affects WBCE CMS where the password generation mechanism uses PHP's rand() function instead of cryptographically secure alternatives, making generated passwords predictable and susceptible to brute-force or sequence-based attacks.
Is CVE-2025-67504 being actively exploited?
No, this vulnerability is not currently tracked on the CISA KEV list and no public exploits are available, though the weakness in password generation presents a real risk if attackers obtain access to the password generation process.
What versions of WBCE CMS are affected by CVE-2025-67504?
WBCE CMS versions 1.6.4 and all earlier versions are affected; version 1.6.5 and later include the security fix.
How do I check if my WBCE CMS installation is vulnerable to CVE-2025-67504?
Check your WBCE CMS version by navigating to the admin panel or running `grep -i 'version' /path/to/wbce/cms/version.php`; if the version is 1.6.4 or below, your installation is vulnerable.
Does Defensia detect CVE-2025-67504?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If PHP and WBCE CMS are installed on a monitored server, CVE-2025-67504 will appear in your dashboard with remediation steps.
Related PHP CVEs
References
- https://cwe.mitre.org/data/definitions/338.html
- https://github.com/WBCE/WBCE_CMS/commit/5d59fe021a5c6e469b1bf192b72ca652e54278f6
- https://github.com/WBCE/WBCE_CMS/releases/tag/1.6.5
- https://github.com/WBCE/WBCE_CMS/security/advisories/GHSA-76gj-pmvx-jcc6
- https://github.com/WBCE/WBCE_CMS/security/advisories/GHSA-76gj-pmvx-jcc6
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2025-67504. Free for 1 server.
Get started free