WP Maps Plugin Arbitrary PHP File Inclusion via AJAX

The WP Maps WordPress plugin before 4.9.7 does not perform a capability check in one of its AJAX actions and does not properly validate a user-controlled path before using it in a file inclusion, allowing users with a Subscriber account to include and execute arbitrary existing local PHP files on the server.

Casky was already ahead

This CVE exploits attack patterns that Casky's 351matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

The WP Maps WordPress plugin before version 4.9.7 contains a critical local file inclusion (LFI) vulnerability stemming from insufficient access controls and inadequate path validation in its AJAX handlers. Specifically, the plugin fails to verify user capabilities before processing certain AJAX requests and does not properly sanitize file paths, enabling subscribers—the lowest privileged user role—to include and execute arbitrary existing PHP files from the server. This vulnerability is particularly dangerous because it bypasses WordPress's standard permission model, turning low-privilege accounts into potential attack vectors for remote code execution and lateral movement within compromised WordPress installations.

Casky's 351 mapped skills leverage Claude's extended reasoning to correlate attack indicators across MITRE ATT&CK's Initial Access (TA0001) and Discovery (TA0007) phases. Practitioners using Casky would observe detection patterns for improper capability checks in AJAX handlers (CWE-22 path traversal signals) and trace execution flows showing unauthenticated or under-authenticated file operations. The platform would flag suspicious AJAX requests to wp-admin/admin-ajax.php with file path parameters, identify lack of `current_user_can()` validation, and highlight instances where user-supplied paths reach `include()` or `require()` functions without proper canonicalization. Security teams gain visibility into both the exploitation chain—how an attacker escalates from subscriber to code execution—and the underlying code patterns that enable the attack, enabling rapid remediation and vulnerability assessment across WordPress environments.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

351 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-16263.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0007

Investigate the attack patterns behind CVE-2026-16263

Casky has 351 skills that investigate the attack patterns behind CVE-2026-16263. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn