Skip to main content
VulnerabilityPublished Updated

CVE-2026-34428: givanz Vvveb · Server-Side Request Forgery (SSRF)

Affects givanz VvvebSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.3 High : upgrade to 1.0.8.1 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.8.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade Vvveb and givanz/Vvveb to 1.0.8.1.

Affected software

ProductAffectedFixed in
givanzVvvebAffected
  • <1.0.8.1
Fixed in
  • 1.0.8.1
GitHubgivanz/Vvvebpkg:github/givanz/VvvebOther threatsAffected
  • <1.0.8.1
Fixed in
  • 1.0.8.1
GitHubVvvebpkg:github/VvvebOther threatsAffected
  • <1.0.8.1
Fixed in
  • 1.0.8.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict backend user access to trusted personnel only and monitor for suspicious activity involving the oEmbedProxy functionality. Avoid exposing the vulnerable versions in untrusted environments.

Description

Vvveb prior to 1.0.8.1 contains a server-side request forgery vulnerability in the oEmbedProxy action of the editor/editor module where the url parameter is passed directly to getUrl() via curl without scheme or destination validation. Authenticated backend users can supply file:// URLs to read arbitrary files readable by the web server process or http:// URLs targeting internal network addresses to probe internal services, with response bodies returned directly to the caller.

References

Community reviews

Loading reviews…