Skip to main content

WMCMS CVE-2026-108811

| EUVDEUVD-2026-97284 LOW
Information Exposure (CWE-200)
2026-10-12 VulDB GHSA-rm82-qc74-7g6j
2.1
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate with low-privilege account
  2. Exploit
    Send crafted request to /index.php
  3. Execution
    Manipulate path/file parameter for file read
  4. Impact
    Disclose sensitive server file contents

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK

2 techniques across 2 tactics: Collection, Discovery

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated session with at least low-level privileges (PR:L) on the WMCMS 4.446.1257 web application; the attacker then supplies a malicious value in the path/file argument of /index.php to traverse to and read unintended files. Limiting factors: the attacker must first obtain valid low-privileged credentials (no unauthenticated access per the CVSS vector), and impact is confined to information disclosure - no write, code-execution, or availability effect. The flaw is reachable over the network against a standard deployment with no special non-default configuration indicated in the description.

Impact

This is a moderate-risk, low-priority issue in practice. The CVSS 4.0 base vector (AV:N/AC:L/AT:N/PR:L/UI:N) describes a remotely reachable, low-complexity attack requiring low-level authentication (PR:L) with limited confidentiality impact (VC:L) and no integrity or availability impact. The exploit maturity is marked E:P (proof-of-concept), consistent with the publicly available exploit code on GitHub, so publicly available exploit code exists but there is no public exploit confirmed as weaponized. No CISA KEV listing and no EPSS score were provided in the input, so there is no signal of active or widespread exploitation - absence of these should not be read as either high or low exploitation likelihood, only as missing data. A notable conflict: the vendor/VulDB rated confidentiality as Low (VC:L), yet the public exploit and its GitHub title describe an *arbitrary file read* primitive, which typically enables reading sensitive files (configuration, credentials) and would justify a High confidentiality rating - verify the true read scope against the PoC before finalizing severity. The authentication requirement (PR:L) is the main factor limiting real-world risk: an attacker needs at least a low-privileged account, making this less attractive than an unauthenticated flaw. Net assessment: a genuine but second-tier vulnerability, not an emergency, absent any KEV/EPSS evidence of in-the-wild use.

Exploit ScenarioDerived

An attacker who holds a low-privileged account on a WMCMS 4.446.1257 instance sends a crafted HTTP request to /index.php, manipulating the path/file argument to point at files outside the intended scope. Because public proof-of-concept exploit code is available on GitHub, the attacker can read server-side files such as configuration or source containing secrets, enabling further disclosure. Low attack complexity and network reachability make the request trivial to replay once authenticated.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 12, 2026

Authenticated path traversal in WMCMS 4.446.1257 lets any user holding a low-privileged account read files outside the intended web directory by manipulating the path/file argument of /index.php, exposing source code, configuration, and credential material on the host. The flaw is network-reachable with no user interaction, and publicly available exploit code exists - a GitHub proof-of-concept repository dedicated to this exact build - so unpatched instances with weak, default, or shared credentials are the realistic targets. Impact is bounded to confidentiality (no write, no code execution, no availability effect), and our independent assessment rates this a moderate-risk, low-priority issue in practice because a valid session is a prerequisite.

RemediationAI

At time of analysis no vendor-released patch for WMCMS 4.446.1257 has been identified; the only public sources are the VulDB entry (https://vuldb.com/vuln/416588) and the proof-of-concept repository (https://github.com/ants01/WMCMSV4.446.1257-There-is-an-arbitrary-file-read-vulnerability), neither of which publishes a fixed version, so remediation must be compensatory for now. Treat the path/file argument as hostile input at the edge: add a WAF or reverse-proxy rule that rejects requests to /index.php whose path/file value contains traversal sequences or absolute paths (../, encoded variants such as ..%2f or double-encoded %252e%252e, and leading slashes), accepting the trade-offs that regex-based filtering is bypassable with novel encodings and can break legitimate nested template or asset references, so pair it with request logging and alerting on 200 responses to /index.php carrying path parameters rather than relying on it alone. Shrink the blast radius by running the PHP worker under a dedicated low-privileged OS account and by relocating configuration files, database credential files, and backups outside the web root or restricting their permissions so the web user cannot read them, testing in staging first because plugins and admin features may depend on those files being accessible. Because exploitation requires only low-privileged credentials, credential hygiene is the highest-leverage control: rotate default and weak passwords, disable dormant and shared accounts, and move the authenticated CMS surface behind a management VPN or IP allowlist, at the cost of reduced remote convenience for legitimate editors. If the deployment does not use the dynamic path/file handling exposed by /index.php, removing or routing around that dispatcher eliminates the attack path entirely, with the obvious trade-off of losing whatever functionality depends on it.

Affected VersionsENISA

WMCMS 4.446.1257

Affected Packages

euvd wmcms no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This is an information-disclosure weakness (CWE-200) rooted in unsanitized path handling rather than an injection or memory-safety bug: the PHP-based WMCMS front controller at /index.php takes a caller-supplied path/file argument and passes it toward a file-read operation without canonicalizing or allowlisting the resolved path, so traversal sequences such as ../ escape the intended directory and the application returns any file the web server process can read. The exploitation primitive is strictly read-only, which is why the integrity and availability sub-scores remain unaffected. Both the CNA's CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N, with E:P marking confirmed proof-of-concept code) and our independent CVSS 3.1 assessment (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) agree on the prerequisites - network reachability, low attack complexity, no user interaction, and, because PR:L is present in the vector, an authenticated session with at least low privileges that must be obtained before traversal is attempted. The two vectors diverge on confidentiality (VC:L versus C:H), and that gap is operationally meaningful: the real blast radius equals whatever the web process can read, which on a typical PHP CMS deployment includes configuration and credential files whose disclosure can be chained into database access, while a hardened host with tightly scoped file permissions limits the leak to templates and content. The CPE record (cpe:2.3:a:n/a:wmcms:*:*:*:*:*:*:*:*) uses a wildcard version and an unregistered vendor field, so no vendor-confirmed fixed build or bounded vulnerable range is available for cross-checking, and the always-wildcard version means the vulnerability is treated as applying to every release the identifier covers.

Know when Wmcms gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 2.1 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
vuln.today AI 6.5 MEDIUM

Network-reachable, low-complexity, authenticated (PR:L) arbitrary file read warrants C:H since arbitrary reads expose sensitive files; no integrity or availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

3
Severity Changed
Oct 12, 2026 - 08:22 NVD
MEDIUM LOW
CVSS changed
Oct 12, 2026 - 08:22 NVD
5.3 (MEDIUM) 2.1 (LOW)
CVE Published
Oct 12, 2026 - 07:15 cve.org
MEDIUM 5.3

DescriptionCVE.org

A weakness has been identified in WMCMS 4.446.1257. The affected element is an unknown function of the file /index.php. This manipulation of the argument path/file causes information disclosure. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be used for attacks.

Threat Intelligence Overview

EPSS Score
0.2%
Top 91% exploitable
Prevalence
Rare
obscure lightweight CMS, minimal enterprise or production footprint
Exploit
POC
Public exploit code exists
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +10
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy