Authenticated file read via unvalidated oEmbed URL
Published Apr 20, 2026 · Updated Apr 20, 2026
Server-side request forgery in Vvveb before 1.0.8.1 allows remote authenticated users to read server files or probe internal services. The editor/editor oEmbedProxy action passes the url parameter directly to getUrl(), which uses cURL without validating the scheme or destination. Backend access is required, and responses expose files readable by the web server process or data returned by reachable internal services.
Summary
What happened
Server-side request forgery in Vvveb before 1.0.8.1 allows remote authenticated users to read server files or probe internal services. The editor/editor oEmbedProxy action passes the url parameter directly to getUrl(), which uses cURL without validating the scheme or destination. Backend access is required, and responses expose files readable by the web server process or data returned by reachable internal services.
The record
- CVE
- CVE-2026-34428
- Published
- Apr 20, 2026
- Updated
- Apr 20, 2026
- Vendor
- givanz
- Product
- Vvveb
- Classifications
- CWE-918, T1005, T1046
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 20, 2026CVE publishedPublication date reported by the CVE source.
- Apr 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.0.8.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo