Quick answers
- Is CVE-2026-35185 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-35185 being exploited in the wild.
- How severe is CVE-2026-35185?
- High severity, with a CVSS score of 7.5, published 6 April 2026.
- Which products and versions are affected?
- Haxtheweb HAX CMS < 25.0.0.
- Is there a fix for CVE-2026-35185?
- A patch was published on 2026-04-06: Fix released in version 25.0.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-35185 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-35185?
- Check whether you run Haxtheweb HAX CMS or Psu Haxiam 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
The Apache mod_status endpoint (/server-status) is enabled and accessible without authentication in HAX CMS (HAXiam) versions prior to 25.0.0. This endpoint exposes real-time application data, including 'user_token' authentication credentials passed in query parameters, client IP addresses, and internal API request paths. Additionally, it reveals server-side metadata such as Apache/OpenSSL versions and server load statistics. An unauthenticated remote attacker can exploit this to obtain active session tokens for account takeover or perform reconnaissance on the internal infrastructure. The issue is resolved in version 25.0.0.
Affected products
- haxtheweb HAXiam / HAX CMS < 25.0.0
Timeline
- 2026-04-01: advisory: GitHub Security Advisory published by vendor
- 2026-04-06: disclosed: CVE published to NVD
- 2026-04-06: patched: Fix released in version 25.0.0