Quick answers
- Is CVE-2026-41928 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-41928 being exploited in the wild.
- How severe is CVE-2026-41928?
- Medium severity, with a CVSS score of 5.3, published 7 May 2026.
- Which products and versions are affected?
- givanz Vvveb < 1.0.8.2.
- Is there a fix for CVE-2026-41928?
- A patch was published on 2026-05-07: Fix committed to GitHub repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-41928 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-41928?
- 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 information disclosure vulnerability exists in the Vvveb cron controller (app/controller/cron.php) due to the presence of test code that inadvertently exposes the secret cron URL and key. An unauthenticated remote attacker can access the cron controller and retrieve the secret key from the HTTP response. With this key, the attacker can bypass intended access controls to trigger scheduled task execution (cron jobs) arbitrarily. The issue is classified as CWE-497 and was addressed in version 1.0.8.2 by removing the debug/test code that displayed the URL.
Affected products
- givanz Vvveb < 1.0.8.2
Timeline
- 2026-05-07: disclosed: Initial disclosure by VulnCheck
- 2026-05-07: advisory: NVD publication date
- 2026-05-07: patched: Fix committed to GitHub repository