Quick answers
- Is CVE-2026-41933 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-41933 being exploited in the wild.
- How severe is CVE-2026-41933?
- Medium severity, with a CVSS score of 5.3, published 14 May 2026.
- Which products and versions are affected?
- Vvveb before 1.0.8.3.
- Is there a fix for CVE-2026-41933?
- A patch was published on 2026-05-13: Version 1.0.8.3 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-41933 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-41933?
- Check whether you run Vvveb 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 directory listing vulnerability (CWE-548) exists in Vvveb versions prior to 1.0.8.3 due to missing 'Options -Indexes' directives in several .htaccess files across the application. An unauthenticated remote attacker can exploit this by directly navigating to specific directory paths such as admin assets, plugins, themes, and media folders. Successful exploitation allows the attacker to view file metadata and unrendered admin templates, which may contain sensitive route maps and internal application logic. The issue was addressed in version 1.0.8.3 by adding proper directory indexing restrictions to the affected .htaccess files.
Affected products
- givanz Vvveb before 1.0.8.3
Timeline
- 2026-05-13: patched: Version 1.0.8.3 released
- 2026-05-14: disclosed: Initial vulnerability disclosure
- 2026-05-14: advisory: NVD publication date