CVE
Vvveb remote code execution in media upload via .phar bypass
- 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. Vvveb before 1.0.9.0 Attacker must be an authenticated administrator with access to the Media Manager The server must run .phar files through PHP (Apache with mod_php by default, or nginx/PHP-FPM with .phar mapped to the PHP handler)
- 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
- 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? →
- 17/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, contains a flaw in its media upload code where a denylist misconfiguration lets an authenticated administrator upload .phar PHP files. An attacker who can log in as an administrator over the network can use a disguised webshell to run arbitrary operating system commands as the web-server user.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Vvveb before 1.0.9.0 contains a denylist bypass in system/traits/media.php where '.phar' is misconfigured with a leading dot, allowing authenticated administrators to upload .phar PHP files. Attackers can upload a GIF magic-byte polyglot webshell bypassing binary inspection and execute arbitrary OS commands as the web-server user.
Who should check
Teams running Vvveb CMS before 1.0.9.0 on Apache with mod_php or on PHP-FPM with .phar mapped to PHP, plus admins with Media Manager access.
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
- Severity9.4/10CVSS 9.4
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Vvveb before 1.0.9.0 Attacker must be an authenticated administrator with access to the Media Manager The server must run .phar files through PHP (Apache with mod_php by default, or nginx/PHP-FPM with .phar mapped to the PHP handler)Upgrade 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-126380 (Vvveb before 1.0.9.0 RCE via .phar Extension Denylist Bypass in Media Upload), 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-126380 (entry last updated 2026-11-13):
Affected:
- givanz Vvveb: fixed in 1.0.9.0
Fixed versions: 1.0.9.0.
Conditions (all must be true for the bug to be hit):
- Vvveb before 1.0.9.0 (source: https://www.vulncheck.com/advisories/vvveb-before-1.0.9.0-rce-via-phar-extension-denylist-bypass-in-media-upload)
- Attacker must be an authenticated administrator with access to the Media Manager (source: https://github.com/givanz/Vvveb/security/advisories/GHSA-hcpj-pcpx-2744)
- The server must run .phar files through PHP (Apache with mod_php by default, or nginx/PHP-FPM with .phar mapped to the PHP handler) (source: https://github.com/givanz/Vvveb/security/advisories/GHSA-hcpj-pcpx-2744)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-126380 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126380 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-hcpj-pcpx-2744
- https://github.com/givanz/Vvveb/commit/638a6c6f5a7a7f7ff4c65f996894f400d8fb8e77
- https://www.vulncheck.com/advisories/vvveb-before-1.0.9.0-rce-via-phar-extension-denylist-bypass-in-media-upload
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-126380
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-126380"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- givanz Vvveb
fixed in 1.0.9.0
Evidence 5
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126380
Is CVE-2026-126380 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?
Vvveb's Media Manager denylist does not block the .phar extension, so an authenticated administrator can upload a .phar PHP webshell. That file can then run arbitrary OS commands on the server as the web-server user.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-126380?
Vvveb: before 1.0.9.0.Source: cve.now feed data
Am I affected, and how do I check?
Vvveb versions before 1.0.9.0 are affected. The bug matters only where the server runs .phar files through PHP, such as Apache with mod_php by default or nginx/PHP-FPM with .phar mapped to the PHP handler. To check, look at the Vvveb version in the admin panel or its release files, and check the server's PHP handler configuration for .phar.Source: vulncheck.com, github.com
How do I fix CVE-2026-126380?
Upgrade Vvveb to version 1.0.9.0 or later, which is the fixed version.Source: vulncheck.com, github.com