Skip to main content
Vulnerability Database/CVE-2026-104899

CVE-2026-104899: GeoDirectory WordPress Plugin RCE Vulnerability

CVE-2026-104899 is a remote code execution vulnerability in the GeoDirectory WordPress plugin allowing unauthenticated attackers to execute arbitrary PHP code. This article covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-104899 Overview

CVE-2026-104899 is a Local File Inclusion (LFI) vulnerability in the GeoDirectory – WP Business Directory Plugin and Classified Listings Directory plugin for WordPress. The flaw affects all versions up to and including 2.8.187 and is reachable through the design_type parameter. Unauthenticated attackers can include and execute arbitrary .php files on the server, enabling access control bypass, sensitive data disclosure, and code execution when attacker-controlled .php files can be placed on disk. The required geodir_basic_nonce is localized to every public frontend page via the geodir_params script object, so the nonce check offers no meaningful barrier to exploitation.

Critical Impact

Unauthenticated remote attackers can include arbitrary PHP files and execute code within the WordPress process, leading to full site compromise.

Affected Products

  • GeoDirectory – WP Business Directory Plugin and Classified Listings Directory for WordPress
  • All versions up to and including 2.8.187
  • Fixed in version 2.8.188

Discovery Timeline

  • 2026-10-10 - CVE-2026-104899 published to NVD
  • 2026-10-13 - Last updated in NVD database

Technical Details for CVE-2026-104899

Vulnerability Analysis

The vulnerability is classified under CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program. The plugin passes the attacker-controlled design_type parameter into template-resolution logic that ultimately feeds a PHP include-style call. Because the parameter value is used to construct the template path without strict allow-listing, an attacker can direct the loader to any .php file reachable from the server filesystem. Successful inclusion causes the target file to execute within the WordPress runtime, inheriting the privileges of the PHP worker.

Root Cause

The affected code paths in includes/class-geodir-ajax.php and includes/template-functions.php resolve a template name derived from design_type and then call file_exists() on the located path before including it. In vulnerable versions, the located path is not validated against a fixed set of permitted templates, and the nonce gate relies on geodir_basic_nonce, which is published to every anonymous visitor through the geodir_params script object. The combination of a trivially obtainable nonce and unconstrained template resolution converts a template loader into an arbitrary file include primitive.

Attack Vector

An unauthenticated attacker first fetches any public page of the vulnerable WordPress site to extract the geodir_basic_nonce from the embedded geodir_params JavaScript object. The attacker then issues an AJAX request to the GeoDirectory endpoint with a crafted design_type value pointing at a .php file already on the server, such as a plugin or uploaded media file. The server includes and executes that file inside the WordPress process. In environments where arbitrary .php content can be written (via other upload flaws, log poisoning, or writable paths), the attacker achieves remote code execution.

php
// Patch excerpt - includes/template-functions.php (2.8.188)
$located = geodir_locate_template( $template_name, $template_path, $default_path );

- if ( ! file_exists( $located ) ) {
+ if ( ! $located || ! file_exists( $located ) ) {
    geodir_doing_it_wrong( __FUNCTION__, sprintf( __( '%s does not exist.', 'geodirectory' ), '<code>' . $located . '</code>' ), '2.1' );

    return;

Source: GeoDirectory commit 2357d640. The fix hardens template resolution so that empty or unresolved template names short-circuit before any include is attempted.

Stop Remote Code Execution Before It Runs

Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.

Stop Exploit Attempts

Detection Methods for CVE-2026-104899

Indicators of Compromise

  • Unexpected HTTP POST requests to admin-ajax.php with action parameters handled by GeoDirectory and a non-standard design_type value.
  • Path traversal sequences (../) or absolute filesystem paths observed in the design_type parameter in web server access logs.
  • New or modified PHP files in wp-content/uploads/ or other writable directories immediately following suspicious GeoDirectory AJAX traffic.
  • Outbound connections from the PHP-FPM or web server process to attacker infrastructure shortly after a crafted request.

Detection Strategies

  • Inspect WordPress and web server logs for requests to GeoDirectory AJAX endpoints containing suspicious design_type values that reference file paths rather than known template identifiers.
  • Deploy a Web Application Firewall (WAF) rule that blocks or alerts on design_type values containing /, \, .., or .php.
  • Monitor for PHP include/require events referencing files outside the plugin's expected template directories using endpoint telemetry.

Monitoring Recommendations

  • Alert on child processes spawned by the PHP interpreter, including shells, curl, wget, and system reconnaissance utilities.
  • Track file integrity on the WordPress document root and wp-content/plugins/geodirectory/ to detect webshell creation or plugin tampering.
  • Correlate frontend page loads that expose geodir_params with subsequent AJAX requests from the same client that carry anomalous design_type values.

How to Mitigate CVE-2026-104899

Immediate Actions Required

  • Upgrade the GeoDirectory plugin to version 2.8.188 or later on every WordPress site where it is installed.
  • Audit wp-content/uploads/ and other writable directories for unauthorized .php files and remove any that are not expected.
  • Rotate WordPress administrator credentials and secret keys if evidence of exploitation is found.

Patch Information

The vendor fix is included in GeoDirectory 2.8.188 and is documented in the upstream GeoDirectory commit 2357d640, with related template handling changes referenced in the WordPress Trac changeset 3725126 and the Wordfence advisory.

Workarounds

  • Deactivate the GeoDirectory plugin until the patched version can be deployed.
  • Add a WAF rule that denies any request where the design_type parameter contains .php, path separators, or traversal sequences.
  • Enforce open_basedir and disable_functions in PHP configuration to constrain which files the WordPress worker can include and execute.
bash
# Example WAF rule (ModSecurity) to block suspicious design_type values
SecRule ARGS:design_type "@rx (\.\./|\.php$|^/|\\\\)" \
    "id:1049899,phase:2,deny,status:403,log,\
    msg:'CVE-2026-104899 GeoDirectory LFI attempt via design_type'"

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.