CVE-2025-64377

ListingPro < 2.9.10 - Unauthenticated Local File Inclusion

2025-09-12 00:00
Rafie Muhammad

Strategic Overview

Status
Patched in 2.9.10
Affected Theme
ListingPro - WordPress Directory & Listing Theme
Affected Version
< 2.9.10
CVSS
8.1High
Weakness type
CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
CVE
CVE-2025-64377
View all ListingPro - WordPress Directory & Listing Theme vulnerabilities

At a glance

CVE-2025-64377 is a high-severity Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in the ListingPro - WordPress Directory & Listing Theme WordPress theme, affecting versions < 2.9.10. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.9.10; sites on affected versions should update now. Disclosed September 2025, reported by Rafie Muhammad.

Vulnerability Overview

The ListingPro theme for WordPress is vulnerable to Local File Inclusion in versions up to 2.9.10. This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other "safe" file types can be uploaded and included.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')

ListingPro - WordPress Directory & Listing Theme < 2.9.10 carries this weakness at safe, and reaching it takes no account at all. PHP file inclusion means a path used by include or require is built from request data, so the file that gets executed is under the caller's influence.

Including an attacker-influenced file executes its contents, which is why this class is routinely chained with an upload or log-poisoning step to reach code execution. For ListingPro - WordPress Directory & Listing Theme the fix is 2.9.10: builds < 2.9.10 are affected, anything from 2.9.10 onward is not.

Remediation

Update to version 2.9.10, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: ListingPro - WordPress Directory & Listing Theme 2.9.10 closes this, and updating the theme is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

https://www.cve.org/CVERecord?id=CVE-2025-64377https://www.wordfence.com/threat-intel/vulnerabilities/id/97bc8742-f47a-448d-9eb2-8f08c1cb1e07https://nvd.nist.gov/vuln/detail/CVE-2025-64377

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C