Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2024-58349 – Unauthenticated Arbitrary File Upload Leading to RCE – WordPress Travelscape The…

Be the first to know when new zero-days emerge:

Summary

CVE-2024-58349 is a critical arbitrary file upload vulnerability (CWE-434) in the WordPress Travelscape theme v1.0.3, developed by WP Travel Kit. The flaw stems from insufficient validation in the theme’s file upload functionality, allowing unauthenticated remote attackers to upload malicious files — such as PHP webshells — directly to the theme directory and execute them, resulting in full Remote Code Execution (RCE) on the affected WordPress installation. The vulnerability carries a CVSS v3.1 score of 9.8 (Critical) and a CVSS v4.0 score of 9.3 (Critical).

Technical details

  • Root cause: The theme exposes a file upload endpoint (/wp-content/themes/travelscape/json.php) that performs insufficient validation of uploaded file types, failing to restrict dangerous file extensions such as .php.
  • Trigger conditions: No authentication, user interaction, or special configuration is required. The endpoint is reachable over the network on any standard WordPress installation running the affected theme.
  • Attack vector: A remote, unauthenticated attacker sends a crafted HTTP request to the vulnerable upload endpoint, uploading a malicious PHP file (e.g., a webshell) to the theme directory.
  • Impact: Once uploaded, the attacker can directly execute the malicious file via an HTTP request, achieving full Remote Code Execution with the privileges of the web server process — enabling complete compromise of the WordPress installation, including full confidentiality, integrity, and availability impact.
  • Public PoC: A working exploit (EDB-ID:51969, authored by Milad Karimi) has been publicly available on Exploit-DB since April 2024, significantly lowering the barrier to exploitation.

Affected software

  • WordPress Travelscape Theme by WP Travel Kit — versions up to and including 1.0.3

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
    Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CVSS v4.0 Base Score: 9.3 (Critical)
    Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate action: No official patched version has been confirmed by the vendor at this time. Site administrators running the Travelscape theme v1.0.3 should contact WP Travel Kit for an updated version and monitor the official theme repository for a security release.
  • If no patch is available:
    • Remove or disable the Travelscape theme on any internet-facing WordPress installation until a patch is released.
    • Apply server-level controls to block external access to /wp-content/themes/travelscape/json.php (e.g., via .htaccess rules or WAF policies).
    • Implement a Web Application Firewall (WAF) rule to block unauthenticated POST requests to the vulnerable endpoint.
    • Audit the web server’s upload directory for any unrecognized or unexpected PHP files.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge