Quick answers
- Is CVE-2026-46493 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-46493 being exploited in the wild.
- How severe is CVE-2026-46493?
- High severity, with a CVSS score of 7.5, published 5 June 2026.
- Which products and versions are affected?
- Haxtheweb HAX CMS < 26.0.1.
- Is there a fix for CVE-2026-46493?
- A patch was published on 2026-06-05: Version 26.0.1 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-46493 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-46493?
- Check whether you run Haxtheweb HAX CMS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
HAX CMS (specifically the haxcms-php backend) utilizes the PHP `uniqid()` function to generate salts within its `install.php` component. According to PHP documentation, `uniqid()` does not produce cryptographically secure values and is based on the system time, making the resulting salts predictable. This vulnerability is classified as CWE-338 (Use of Cryptographically Weak PRNG). An unauthenticated remote attacker could exploit this predictability to compromise cryptographic operations that rely on these salts, leading to a loss of confidentiality. The issue has been addressed in version 26.0.1 by migrating to a cryptographically secure pseudo-random number generator (CSPRNG).
Affected products
- haxtheweb HAX CMS (PHP backend) < 26.0.1
Timeline
- 2026-05-14: advisory: GitHub Security Advisory GHSA-xg43-xm47-74cp published
- 2026-06-05: disclosed: CVE-2026-46493 published to NVD
- 2026-06-05: patched: Version 26.0.1 released