givanz Vvveb up to 1.0.8.6 Theme Install theme.php validFile unrestricted upload
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $0-$5k | 0.00+ |
Summary
A vulnerability classified as problematic was found in givanz Vvveb up to 1.0.8.6. This affects the function validFile of the file theme.php of the component Theme Install. Such manipulation leads to unrestricted upload.
This vulnerability is referenced as CVE-2026-126378. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability was found in givanz Vvveb up to 1.0.8.6 and classified as problematic. Affected by this issue is the function validFile of the file theme.php of the component Theme Install. The manipulation with an unknown input leads to a unrestricted upload vulnerability. Using CWE to declare the problem leads to CWE-434. The product allows the upload or transfer of dangerous file types that are automatically processed within its environment. Impacted is confidentiality, integrity, and availability. CVE summarizes:
Vvveb through 1.0.8.6 contains a file upload vulnerability in the theme installer validFile() function that uses strpos() instead of strict path matching. Attackers with admin credentials can upload a ZIP containing a PHP file whose path includes /theme.php to achieve remote code execution on nginx deployments.
The advisory is available at github.com. This vulnerability is handled as CVE-2026-126378 since 11/10/2026. The exploitation is known to be easy. The attack may be launched remotely. The exploitation requires an enhanced level of successful authentication. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 11/13/2026). This vulnerability is assigned to T1608.002 by the MITRE ATT&CK project.
By approaching the search of inurl:theme.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
Website
- Product: https://github.com/givanz/Vvveb/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.8
VulDB Base Score: 4.7
VulDB Temp Score: 4.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 9.1
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Unrestricted uploadCWE: CWE-434 / CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Google Hack: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
11/10/2026 CVE reserved11/13/2026 Advisory disclosed
11/13/2026 VulDB entry created
11/13/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Not defined
CNA: VulnCheck
CVE: CVE-2026-126378 (🔒)
GCVE (CVE): GCVE-0-2026-126378
GCVE (VulDB): GCVE-100-436730
Entry
Created: 11/13/2026 11:11Changes: 11/13/2026 11:11 (76)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.