Quick answers
- Is CVE-2026-41937 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-41937 being exploited in the wild.
- How severe is CVE-2026-41937?
- High severity, with a CVSS score of 7.2, published 14 May 2026.
- Which products and versions are affected?
- givanz Vvveb before 1.0.8.3.
- Is there a fix for CVE-2026-41937?
- A patch was published on 2026-05-11: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-41937 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-41937?
- Check whether you run Givanz VvvebJs. 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 unrestricted file upload vulnerability (CWE-434) exists in the plugin upload endpoint of Vvveb. A user with super_admin privileges can upload a malicious ZIP archive containing a 'plugin.php' file with a valid Slug header and a 'public/index.php' file containing arbitrary PHP code. Because the application does not properly validate the contents of the uploaded plugin's public directory, the PHP code can be executed by the web server user through a subsequent unauthenticated HTTP request to the plugin's public path. The vulnerability is addressed in version 1.0.8.3 by validating plugin uploads and ensuring PHP files are not exposed in public folders.
Affected products
- givanz Vvveb before 1.0.8.3
Timeline
- 2026-05-11: patched: Fix committed to repository
- 2026-05-13: advisory: Version 1.0.8.3 released
- 2026-05-14: disclosed: CVE published