LiveActive security incident?Get immediate response
CVE Record

CVE-2026-34428: Vvveb < 1.0.8.1 SSRF via oEmbedProxy

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.

HighCVSS 8.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A logged-in Vvveb backend user can make the server retrieve local files or contact internal systems through the editor’s oEmbedProxy feature. Returned content may expose sensitive files, credentials, configuration, or otherwise unreachable services. The vulnerability affects releases before 1.0.8.1.

Executive priority

Treat this as a high-priority authenticated exposure. Patch internet-facing or sensitive-network deployments promptly, then review backend accounts and request logs. Immediate emergency action is most warranted where administrator credentials may be compromised or Vvveb can reach valuable internal services.

Technical view

CVE-2026-34428 is a CWE-918 server-side request forgery flaw. oEmbedProxy passes the user-controlled url parameter directly to getUrl() and curl without validating its scheme or destination. Authenticated backend users can request file:// resources or internal http:// addresses, and response bodies are returned to them. CVSS 4.0 score: 8.3.

Likely exposure

Exposure requires Vvveb earlier than 1.0.8.1 and access to an authenticated backend account capable of reaching the affected editor action. Risk increases where the web server can read sensitive files, access cloud metadata, or reach trusted internal services.

Exploitation context

The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation nevertheless appears low-complexity for an authenticated backend user, requiring no victim interaction. Compromised, malicious, or excessively provisioned backend accounts are the primary threat context.

Researcher notes

The weakness crosses both filesystem and network trust boundaries because curl receives an unvalidated URL and returns its response. The published fix is associated with release 1.0.8.1 and commit 2d356844f37819bf771e7cd5e12a8686975e0b2b. The bundle provides no evidence of exploitation in the wild.

Mitigation direction

  • Upgrade Vvveb to version 1.0.8.1 or later.
  • Restrict backend access to trusted, necessary users until upgrading.
  • Review vendor release notes and patch details before deployment.
  • Limit the web server’s filesystem permissions and unnecessary internal network access.
  • Rotate exposed credentials if investigation indicates sensitive files were retrieved.

Validation and detection

  • Inventory all Vvveb deployments and confirm their exact installed versions.
  • Verify version 1.0.8.1 or later is running after remediation.
  • Review backend access logs for suspicious oEmbedProxy requests.
  • Investigate requests referencing local-file schemes, loopback addresses, or private network destinations.
  • Confirm only authorized users retain backend editor access.
Prepared
Confidence
high
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-34428 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.3 (4.0)
Known Exploited
No
Published

Vector: 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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.3CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N——VulnCheck
7.7CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N3.14VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

8.3High
CVSS 4.0 vector shape for CVE-2026-34428Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
givanzVvveb0, 2d356844f37819bf771e7cd5e12a8686975e0b2bunaffected
Weakness

CWE details

CWE-918

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs