Quick answers
- Is CVE-2026-39169 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-39169 being exploited in the wild.
- How severe is CVE-2026-39169?
- Informational severity, with a CVSS score of 7.5, published 9 June 2026.
- Which products and versions are affected?
- SEMCMS <= 5.0.
- Is there a fix for CVE-2026-39169?
- 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-39169 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-39169?
- Check whether you run SEMCMS 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
An improper access control vulnerability (CWE-284) exists in SEMCMS versions 5.0 and earlier within the SEMCMS_copy.php file. The component fails to implement authentication or authorization checks, allowing a remote, unauthenticated attacker to trigger the database export functionality by sending a crafted GET request (e.g., using the 'type=dc' parameter). The resulting SQL backup is stored in a predictable location (/backups/semcms.sql) within the web root, where it can be downloaded by the attacker. This leads to the disclosure of the entire database, including administrator credentials and configuration data. Notably, the researcher identified a syntax error in the vulnerable file that may require correction for the exploit to function as intended.
Affected products
- SEMCMS SEMCMS <= 5.0
Timeline
- 2026-06-05: disclosed: Initial researcher disclosure on GitHub Gist
- 2026-06-09: advisory: NVD published the CVE record