LiveActive security incident?Get immediate response
CVE Record

CVE-2026-41933: Vvveb < 1.0.8.3 Directory Listing Information Disclosure

Vvveb before 1.0.8.3 contains a directory listing information disclosure vulnerability that allows unauthenticated attackers to enumerate files and directories by accessing multiple paths lacking proper index directives in .htaccess files. Attackers can access directories such as admin asset paths, plugins, themes, and media folders to view filenames, file sizes, modification timestamps, and unrendered admin templates containing sensitive route maps.

MediumCVSS 6.9Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Publicly reachable Vvveb installations before 1.0.8.3 may reveal directory contents without authentication. Exposed filenames, timestamps, file sizes, plugin and theme details, media paths, and unrendered administrative templates could help attackers map the application and identify further targets. The issue discloses information but is not reported to directly modify data or disrupt service.

Executive priority

Schedule prompt remediation for public-facing systems and include it in the next controlled maintenance window. Escalate priority where sensitive templates, custom plugins, or uploaded media names are exposed. Emergency response is not supported by the supplied evidence because active exploitation and direct integrity or availability impact are not established.

Technical view

CVE-2026-41933 is a CWE-548 directory-listing weakness caused by missing index protections in multiple .htaccess-controlled paths. Unauthenticated remote requests may enumerate admin assets, plugins, themes, media, and administrative templates containing route maps. It has CVSS 4.0 score 6.9 with low confidentiality impact and no stated integrity or availability impact. Vvveb 1.0.8.3 contains the referenced patch.

Likely exposure

Internet-facing Vvveb deployments older than 1.0.8.3 are the primary concern, especially where the web server permits directory indexes and honors the affected path configuration. Deployments already preventing directory browsing may have reduced practical exposure, but this should be validated rather than assumed.

Exploitation context

The weakness requires no authentication, privileges, user interaction, or special conditions, making opportunistic discovery straightforward. However, the supplied record is not in KEV and provides no evidence of active exploitation. The disclosed information may support reconnaissance, but the sources do not establish follow-on compromise.

Researcher notes

The affected range is described as Vvveb before 1.0.8.3, with commit 96ae04c5e4a295e281adc1d02d77444173653deb referenced as the patch boundary. Validate effective server behavior because practical exposure depends on directory-index handling. The bundle does not identify exploited-in-the-wild activity, exposed credentials, or a demonstrated path from listing disclosure to code execution.

Mitigation direction

  • Upgrade Vvveb to version 1.0.8.3 or later using the vendor release guidance.
  • Apply the vendor's referenced patch if an immediate full upgrade is impractical.
  • Disable directory indexing across affected web paths while preparing the permanent update.
  • Review exposed administrative templates and route information for potential secondary risk.

Validation and detection

  • Confirm every deployed Vvveb instance and version, prioritizing publicly reachable installations older than 1.0.8.3.
  • Test representative admin asset, plugin, theme, and media directories without authentication.
  • Verify directory requests no longer return file listings, sizes, timestamps, or template contents.
  • Review access logs for unexpected enumeration of affected directories before and after remediation.
Prepared
Confidence
high
Sources
5

Public sources used

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 · low confidence lookup

CWE-548: 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 lookup
cve · low confidence lookup

CVE-2026-41933 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Official CVE source material

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.

2CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

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.

ScoreVersionSeverityVectorExploitImpactSource
6.9CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N——VulnCheck
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

6.9Medium
CVSS 4.0 vector shape for CVE-2026-41933Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
givanzVvveb0, 96ae04c5e4a295e281adc1d02d77444173653debaffected
Weakness

CWE details

CWE-548

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-548 · source CWE mapping

Exposure of Information Through Directory Listing

Exposure of Information Through Directory Listing represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs