Quick answers
- Is CVE-2026-38934 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-38934 being exploited in the wild.
- How severe is CVE-2026-38934?
- High severity, with a CVSS score of 8.8, published 27 April 2026.
- Which products and versions are affected?
- Diskover Data Diskover Community <= 2.3.5.
- Is there a fix for CVE-2026-38934?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-38934 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-38934?
- Check whether you run Diskover Data Diskover Community 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
A Cross-Site Request Forgery (CSRF) vulnerability exists in the 'public/settings_process.php' component of diskover-community versions 2.3.5 and prior. The application fails to implement or validate CSRF tokens for sensitive POST requests, specifically within the 'webotherform' form handler. An attacker can exploit this by inducing an authenticated administrator to visit a malicious webpage that submits a hidden form to the vulnerable endpoint. By setting the 'LOGIN_REQUIRED' parameter to 'false', the attacker can disable authentication for the entire application, leading to unauthorized access to the dashboard and underlying Elasticsearch data. Mitigation requires implementing per-session CSRF tokens and validating them on all state-changing requests.
Affected products
- diskoverdata diskover-community <= 2.3.5
Timeline
- 2026-04-27: disclosed: Initial NVD publication and researcher write-up released.