CVE
Vvveb server-side request forgery in oEmbed proxy
Affects Vvveb 1.0.8.6 up to 1.0.9.0 for authenticated admin-panel users with access to the editor oEmbed proxy. Fixed in 1.0.9.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.0.9.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Requests must use non-443 URLs (for example http:// URLs or explicit non-443 ports), which the 443-only pinning does not cover Attacker must be an authenticated admin-panel user with access to the editor oEmbed proxy Affects Vvveb 1.0.8.6 up to, but not including, 1.0.9.0
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.35% · 29th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Vvveb, a content management system from givanz, has a server-side request forgery flaw in its editor oEmbed proxy that an attacker can reach over the network, but only after logging in with administrator-level access. Using a DNS rebinding hostname in the url parameter, the attacker can read loopback services, internal panels, and cloud metadata credentials.
Read the original description
Vvveb 1.0.8.6 contains an incomplete server-side request forgery fix that allows authenticated admin users to bypass DNS pinning by requesting non-443 URLs. Attackers can supply a rebinding hostname to the editor oEmbedProxy url parameter to read loopback services, internal panels, and cloud metadata credentials.
Who should check
Teams running Vvveb 1.0.8.6 (Composer package vvveb) where admin or editor users can reach the editor oEmbed proxy
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Requests must use non-443 URLs (for example http:// URLs or explicit non-443 ports), which the 443-only pinning does not cover Attacker must be an authenticated admin-panel user with access to the editor oEmbed proxy Affects Vvveb 1.0.8.6 up to, but not including, 1.0.9.0Upgrade to a fixed version: 1.0.9.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126379 (Vvveb 1.0.8.6 SSRF via oEmbed Proxy DNS Rebinding), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126379 (entry last updated 2026-11-13):
Affected:
- givanz Vvveb: from 1.0.8.6, fixed in 1.0.9.0
Fixed versions: 1.0.9.0.
Conditions (all must be true for the bug to be hit):
- Requests must use non-443 URLs (for example http:// URLs or explicit non-443 ports), which the 443-only pinning does not cover (source: https://github.com/givanz/Vvveb/security/advisories/GHSA-42hc-694f-hcqm)
- Attacker must be an authenticated admin-panel user with access to the editor oEmbed proxy (source: https://github.com/givanz/Vvveb/security/advisories/GHSA-42hc-694f-hcqm)
- Affects Vvveb 1.0.8.6 up to, but not including, 1.0.9.0 (source: https://www.vulncheck.com/advisories/vvveb-1.0.8.6-ssrf-via-oembed-proxy-dns-rebinding)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-126379 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126379 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/givanz/Vvveb/security/advisories/GHSA-42hc-694f-hcqm
- https://www.vulncheck.com/advisories/vvveb-1.0.8.6-ssrf-via-oembed-proxy-dns-rebinding
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126379
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126379"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- givanz Vvveb
From 1.0.8.6 · fixed in 1.0.9.0
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126379
Is CVE-2026-126379 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An authenticated admin-panel user can make the Vvveb server fetch internal URLs and read the responses. This includes loopback services, internal admin panels, and cloud metadata credentials. The oEmbed proxy's DNS pinning covers only 443 URLs, so other URLs are not pinned to the previously validated IP address.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-126379?
Vvveb: from 1.0.8.6 before 1.0.9.0.Source: cve.now feed data
Am I affected, and how do I check?
Vvveb 1.0.8.6 up to, but not including, 1.0.9.0. The issue involves the editor oEmbed proxy and requests that use non-443 URLs, such as http:// URLs or explicit non-443 ports. Compare the installed Vvveb version with this range to check the version side.Source: github.com, vulncheck.com
How do I fix CVE-2026-126379?
Upgrade Vvveb to 1.0.9.0 or later, which is the fixed version in the product range.Source: github.com, vulncheck.com