Vvveb before 1.0.8.3 contains an unrestricted file upload vulnerability in the plugin upload endpoint that allows super_admin users to execute arbitrary PHP code by uploading a malicious plugin ZIP file. Attackers can craft a ZIP containing a plugin.php with a valid Slug header and a public/index.php file with arbitrary PHP code, which executes as the web server user once accessed via subsequent unauthenticated HTTP requests to the plugin's public path.
Security readout for executives and security teams
Plain-English summary
Vvveb versions before 1.0.8.3 allow a super administrator to upload a crafted plugin that runs PHP code as the web server user. This can compromise website data, content, credentials, and availability. The initial action requires a highly privileged account, but the uploaded code can subsequently be reached without authentication.
Executive priority
Prioritize remediation for public-facing Vvveb systems and environments holding sensitive data. Treat suspected super_admin compromise as a potential server compromise and investigate promptly. The privilege prerequisite lowers opportunistic risk, but successful exploitation provides complete confidentiality, integrity, and availability impact within the web server account's reach.
Technical view
The plugin upload endpoint insufficiently restricts plugin ZIP contents. A crafted archive containing valid plugin metadata and PHP beneath the plugin's public path can place executable code in a web-accessible location. Accessing that path triggers remote code execution with web server permissions. The issue is classified under CWE-434 and CWE-61 and scores 8.6 under CVSS 4.0.
Likely exposure
Internet-accessible Vvveb installations below 1.0.8.3 are affected when an attacker controls or compromises a super_admin account. Exposure is more consequential where the web server can access sensitive configuration, credentials, customer data, or writable application content. The supplied version metadata is unusual, but the description clearly identifies releases before 1.0.8.3.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not identified as a CISA KEV entry. Exploitation requires high privileges for the malicious plugin upload, reducing initial accessibility. However, stolen administrator credentials or a malicious administrator could convert that access into persistent server-side code execution, with later requests to the uploaded path requiring no authentication.
Researcher notes
The provided CVSS 4.0 vector is AV:N/AC:L/AT:N/PR:H/UI:N with high vulnerable-system impacts and no subsequent-system impacts. Public evidence attributes the flaw to unrestricted plugin archive handling and web-accessible PHP placement. The structured affected-version entry contains an atypical commit identifier, so confirm exact version boundaries against the linked release and patch records.
Mitigation direction
Upgrade affected Vvveb installations to version 1.0.8.3 or later.
Follow the vendor release notes and patch guidance for deployment details.
Restrict super_admin access and rotate credentials suspected of compromise.
Temporarily limit plugin installation privileges until upgrading is complete.
Review web server permissions to reduce access to sensitive files and services.
Validation and detection
Confirm the deployed Vvveb version is 1.0.8.3 or later.
Inventory all accounts holding super_admin privileges and verify their necessity.
Review plugin directories for unexpected, recently added, or modified PHP files.
Examine plugin-upload and public-path access logs for suspicious activity.
Verify the production code contains the vendor's referenced security commit.
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-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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: total
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-434 · source CWE mapping
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
UNIX Symbolic Link (Symlink) Following represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.