Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Contributor-level account
-
DeliverySend crafted request with traversal sequences
-
ExploitBypass path canonicalization in plugin
-
ExecutionRead arbitrary server files
-
ImpactExfiltrate wp-config.php credentials
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path traversal prevention
|
| Exploitation Conditions | Requires an authenticated WordPress account with at least Contributor privileges on a site running the Creator LMS plugin version 1.2.19 or earlier (PR:L). Exploitation is remote over the network (AV:N) with no user interaction (UI:N), but attack complexity is rated high (AC:H), indicating the traversal depends on specific, not-guaranteed conditions to succeed reliably. The principal limiting factors are the need for a valid low-privilege account (self-registration must be enabled or the account otherwise obtained) and the elevated complexity, which together narrow this well below an unauthenticated default-configuration attack. |
| Impact | This is a moderate-priority issue that reads higher than its real-world risk. The CVSS 7.5 is inflated primarily by the vendor's full C:H/I:H/A:H triad, but the vulnerability is a CWE-35 path traversal in a WordPress plugin - a class that in practice yields arbitrary file READ (confidentiality), not the write/integrity or availability impact the vector claims. The vector itself carries two meaningful brakes: AC:H (high attack complexity, implying the traversal is not trivially reliable) and PR:L (a valid Contributor-level account is required), so this is not an unauthenticated internet-wide exploit. Exploitation signals are all cold: no EPSS score provided, no CISA KEV listing, and no public POC identified at time of analysis, which is typical for a freshly Patchstack-disclosed WordPress plugin CVE. Weighing these together, the practical risk is a low-to-medium authenticated file-disclosure bug that could leak wp-config.php credentials or other sensitive files, but requires an attacker to already hold a Contributor account and clear a non-trivial exploitation hurdle. Note the impact conflict: vendor scores C:H/I:H/A:H, but a path-traversal read primitive realistically supports C:H with only marginal I/A - verify the actual sink with the vendor advisory before treating this as a write/RCE-adjacent flaw. |
| Exploit ScenarioDerived | An attacker who has registered or obtained a WordPress Contributor account on a site running Creator LMS <= 1.2.19 submits a crafted request to a plugin endpoint containing directory-traversal sequences (e.g. ../../) in a file-path parameter. Because input is not properly canonicalized, the plugin resolves the path outside its intended directory and returns the contents of an arbitrary server file such as wp-config.php, exposing database credentials and secret keys. No public exploit code is currently available, and the CVSS AC:H rating suggests the traversal requires specific conditions to trigger reliably. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 30, 2026
Authenticated path traversal in the WordPress Creator LMS plugin (WPFunnels) affects all versions up to and including 1.2.19 and allows a user holding only Contributor-level privileges to manipulate file paths and reach files outside the intended directory, primarily exposing sensitive data with limited integrity and availability effects. Exploitation requires a valid low-privilege account - self-registration must be enabled or an account otherwise obtained - and is rated high complexity (AC:H), meaning success depends on specific, not-guaranteed conditions; the issue is remote, needs no user interaction, and no public exploit has been identified at time of analysis. It is not confirmed actively exploited (no CISA KEV listing), and while the vendor-supplied CVSS of 7.5 and the scorer's high confidentiality/integrity/availability ratings read alarming, the practical risk is moderate because the attack is gated behind an authenticated Contributor role and elevated complexity.
RemediationAI
No vendor-released patch or fixed version is identified in the available data, so remediation starts with checking the WPFunnels/Creator LMS release notes and the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/creatorlms/vulnerability/wordpress-creator-lms-plugin-1-2-19-path-traversal-vulnerability?_s_id=cve for a version above 1.2.19 and upgrading as soon as one is published; until then, treat 1.2.19 and earlier as unpatched. The most effective compensating control is to shrink the attack surface at the privilege layer: disable open WordPress registration or restrict registration to roles below Contributor, and audit existing accounts to remove Contributor or higher capabilities from users who do not need them, accepting that this may disrupt legitimate course-authoring workflows. If the LMS functionality is not currently required, deactivating the plugin removes the vulnerable code path entirely, at the cost of losing all course and enrollment features. A virtual patching or WAF layer can also be used to block HTTP requests containing traversal-style sequences such as '.../...//' and encoded '../' variants to plugin endpoints, with the caveat that generic traversal signatures produce false positives and must be tuned. Because exploitation requires high complexity and an authenticated low-privilege account rather than an unauthenticated vector, prioritizing the patch on sites with public registration enabled is the highest-value triage step.
Affected VersionsENISA
Affected Packages
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
The root cause is CWE-35, the path traversal variant commonly written as '.../...//', in which deliberately malformed relative-path sequences survive naive input sanitization - typically a check that only strips or blocks straight '../' tokens - and are then normalized by the underlying filesystem or PHP path functions into a directory-escaping path. Creator LMS is a WordPress LMS plugin published by WPFunnels and catalogued under the CPE cpe:2.3:a:wpfunnels:creator_lms, with the version field wildcarded to indicate the entire release line through 1.2.19 is affected. Because the vulnerable code executes inside the WordPress request lifecycle, reachability depends on plugin endpoints and the capability checks applied to them: the assessed vector (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:L) confirms a network-reachable path that a Contributor-level role (PR:L) can trigger without user interaction (UI:N), but the high attack complexity reflects that the traversal only succeeds under particular path/encoding conditions rather than in a default, deterministic way. The confined scope (S:U) and the high confidentiality weighting relative to lower integrity and availability weighting indicate the dominant impact is unauthorized read of files outside the intended plugin directory, with only limited write or disruption potential.
Know when Creator Lms 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
AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Contributor login (PR:L) and a non-trivial traversal (AC:H); a path-traversal read yields C:H but only marginal integrity/availability, so I:L/A:L rather than the vendor's I:H/A:H.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Contributor Path Traversal in Creator LMS <= 1.2.19 versions.
Executive ViewAI
WordPress sites running the Creator LMS (WPFunnels) plugin through version 1.2.19 face a high-severity path traversal issue that could expose sensitive files to a low-privilege Contributor account, with no vendor-released patch identified at time of analysis. Because exploitation requires a valid account and specific conditions, and no public exploit identified at time of analysis, the practical organizational risk is moderate but warrants immediate inventory and access-control review. Leadership should care if affected LMS sites host student, customer, or configuration data, as unauthorized file access could lead to data disclosure and compliance concerns.
No vendor-released patch identified at time of analysis. Interim mitigations: deactivate Creator LMS (WPFunnels) if not essential, restrict or disable Contributor self-registration and remove unnecessary Contributor accounts, enforce least privilege, deploy WAF/virtual patching rules to block path traversal attempts, monitor file access and logs for suspicious activity, and conduct a sensitive-data exposure review.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
More in Creator Lms
View allArbitrary file upload in the WordPress plugin Creator LMS (by WPFunnels) versions 1.2.21 and earlier lets an authenticat
An Incorrect Privilege Assignment vulnerability exists in WPFunnels Creator LMS plugin (versions up to and including 1.1
WordPress sites running the WPFunnels Creator LMS plugin at version 1.2.19 or earlier expose an authenticated manipulati
EUVD-2026-89908
GHSA-r9h2-gpr8-x9mm
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB