Security readout for executives and security teams
Plain-English summary
Vvveb versions before 1.0.8.2 allow several non-administrator roles to turn code-editor access into full server-side code execution. Successful compromise could expose data, alter website content, disrupt service, and provide continuing access through files reachable from the internet.
Executive priority
Prioritize remediation for public-facing installations and environments granting code-editor access to delegated users. The 8.8 severity and potential full confidentiality, integrity, and availability impact justify urgent treatment, although the supplied sources do not show active exploitation. Investigate for compromise alongside upgrading where exposed accounts may be untrusted or compromised.
Technical view
Insufficient extension restrictions in Vvveb’s admin code editor permit editor, author, contributor, or site_admin users to create a .htaccess rule and upload server-executable PHP content under another extension. A later unauthenticated HTTP request can trigger that content. CVSS 3.1 rates this 8.8: network-accessible, low complexity, low privileges, no user interaction.
Likely exposure
Internet-facing Vvveb installations below 1.0.8.2 are exposed when an attacker controls any listed low-privilege account with code-editor access. Exposure depends on the web server honoring .htaccess directives and serving the written files. The supplied evidence does not establish how commonly those conditions occur.
Exploitation context
The source bundle reports no CISA KEV listing and provides no evidence of active exploitation. Exploitation requires prior authentication as an editor, author, contributor, or site_admin, but the resulting malicious file can be triggered without authentication. Treat compromised credentials and untrusted delegated accounts as meaningful risk factors.
Researcher notes
The weakness is classified as CWE-184: an incomplete list of disallowed inputs. The critical chain combines inadequate extension filtering, writable .htaccess configuration, uploaded PHP content, and public HTTP reachability. Validate these prerequisites defensively without executing payloads. The supplied affected-version description is clearer than the sparse affected entry listing version “0.”
Mitigation direction
- Upgrade Vvveb to version 1.0.8.2 or later using vendor guidance.
- Restrict code-editor access until upgrading, especially for delegated low-privilege roles.
- Review and remove unnecessary editor, author, contributor, and site_admin accounts.
- Follow the vendor advisory and patch commit for deployment-specific remediation details.
Validation and detection
- Confirm every Vvveb installation and its exact deployed version.
- Verify version 1.0.8.2 or later is running after remediation.
- Inventory accounts holding editor, author, contributor, or site_admin roles.
- Inspect writable web locations for unexpected .htaccess and executable content.
- Review HTTP and administration logs for suspicious code-editor activity and file requests.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-184: Exact CWE lookup
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.
Open ATT&CK lookupExecution behavior lookup
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.
Open ATT&CK lookupCVE-2026-41934 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/givanz/Vvveb/releases/tag/1.0.8.2CVE reference, VulnCheck · release-notes
- https://github.com/givanz/Vvveb/security/advisories/GHSA-vfjj-gcvv-w248CVE reference, VulnCheck · vendor-advisory
- https://github.com/givanz/Vvveb/commit/1196561276a3f49da5a714fef89ac9a6c6f9e33bCVE reference, VulnCheck · patch
- https://www.vulncheck.com/advisories/vvveb-authenticated-rce-via-code-editorCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incomplete List of Disallowed Inputs
Incomplete List of Disallowed Inputs represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.