Quick answers
- Is CVE-2026-15530 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-15530 being exploited in the wild.
- How severe is CVE-2026-15530?
- Medium severity, with a CVSS score of 5.3, published 13 July 2026.
- Which products and versions are affected?
- WuzhiCMS up to 4.1.0.
- Is there a fix for CVE-2026-15530?
- 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-15530 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-15530?
- Check whether you run WuzhiCMS 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 information disclosure vulnerability exists in WuzhiCMS versions up to 4.1.0 within the Attachment API component. The flaw is located in the config/listimage function of the /index.php?m=attachment&f=index&v=upload endpoint. The root cause is a failure to implement proper authorization checks (CWE-862), allowing unauthenticated remote attackers to trigger the 'action=config' parameter. Successful exploitation enables an attacker to retrieve sensitive system configuration details and file listings. A proof-of-concept has been published, and while the vendor was notified via a GitHub issue, no patch is currently available.
Affected products
- WuzhiCMS WuzhiCMS up to 4.1.0
Timeline
- 2026-07-13: advisory: Initial disclosure by VulDB/NVD
- 2026-07-13: disclosed: Public issue report on GitHub