CVE-2026-80067

MEDIUM CVSS 5.4
Published: 2026-10-29
Modified: 2026-10-29
Enriched via mock
Tenable Plugin

Checking the public Tenable catalog…

AI Threat Summary

CVE-2026-80067 is a moderate vulnerability with a CVSS score of 5.4 affecting the target software. Threat hunters should monitor for exploit attempts and apply vendor patches immediately.

Description

MasterStudy LMS plugin for WordPress before 3.7.50 contains a path traversal vulnerability that allows authenticated Subscriber-level users to import arbitrary WXR XML files by supplying directory traversal sequences in the stm_lms_step parameter passed to the stm_lms_import_sample_data AJAX action, which lacks capability checks and nonce verification. Attackers can traverse the file system to reference a reachable WXR file and have the handler publish its contained posts under their identity, enabling publication of attacker-chosen post type, title, content, and metadata.

Attack Chain
1
Reconnaissance

Attacker scans for vulnerable versions using version banners or PoC scanners

2
Initial Access

Attacker triggers CVE-2026-80067 vulnerability with a crafted request or payload

3
Execution

Vulnerability exploited to perform unauthorized actions on the target system

4
Impact

Depending on vulnerability type, attacker achieves data access, service disruption, or code execution

MITRE ATT&CK Techniques
T1190 Exploit Public-Facing Application
Initial Access

Public-facing application vulnerability exploited for initial access

T1203 Exploitation for Client Execution
Execution

Vulnerability exploited to execute attacker-controlled code

Indicators of Compromise
Type Value Description
user_agent Mozilla/5.0 (compatible; exploit/1.0) Generic exploit scanner user agent pattern
url /api/vuln-endpoint?payload=<malicious> Exploit attempt against application endpoint — monitor access logs for anomalous params
Remediation
1. Apply vendor-supplied security patches immediately. 2. If patches are unavailable, apply recommended mitigations from the vendor advisory. 3. Enable WAF rules or IDS signatures to detect exploitation attempts. 4. Monitor logs for indicators of compromise listed above. 5. Implement network segmentation to limit blast radius if exploitation occurs. 6. Subscribe to vendor security advisories for this product.