CVE-2025-10143: CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in catchthemes Catch Dark Mode
The Catch Dark Mode plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.0 via the 'catch_dark_mode' shortcode. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary .php 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 .php file types can be uploaded and included.
AI Analysis
Technical Summary
CVE-2025-10143 is a Local File Inclusion vulnerability identified in the Catch Dark Mode plugin for WordPress, affecting all versions up to 2.0. The vulnerability arises from improper validation and control of filenames used in PHP include or require statements within the 'catch_dark_mode' shortcode functionality. An attacker with authenticated access at the Contributor role or higher can leverage this flaw to include arbitrary PHP files from the server filesystem. This inclusion leads to execution of any PHP code contained within those files, enabling a range of malicious activities such as bypassing WordPress access controls, reading sensitive configuration or user data, and executing arbitrary commands on the server. The attack vector requires network access and authenticated privileges but does not require user interaction. The CVSS 3.1 base score of 7.5 reflects high severity due to the potential for confidentiality, integrity, and availability impacts. Although no public exploits are currently known, the vulnerability represents a significant risk given the widespread use of WordPress and the Catch Dark Mode plugin. The root cause is classified under CWE-98, indicating improper control of filenames in include/require statements, a common source of LFI vulnerabilities. Without a patch available at the time of disclosure, mitigation relies on access control hardening and monitoring.
Potential Impact
The impact of CVE-2025-10143 is substantial for organizations running WordPress sites with the Catch Dark Mode plugin installed. Successful exploitation allows attackers to execute arbitrary PHP code on the web server, which can lead to full site compromise. This includes bypassing authentication and authorization controls, exposing sensitive user data, modifying website content, deploying web shells, or pivoting to other internal systems. The vulnerability affects the confidentiality, integrity, and availability of affected systems. Given that Contributor-level access is sufficient, attackers who gain low-privilege credentials or exploit other vulnerabilities to escalate privileges can leverage this flaw to gain full control. The lack of user interaction and network-based attack vector increases the risk of automated exploitation once details become public. Organizations may face reputational damage, data breaches, and service disruptions if this vulnerability is exploited.
Mitigation Recommendations
To mitigate CVE-2025-10143, organizations should immediately restrict Contributor and higher roles to trusted users only, minimizing the attack surface. Disable or remove the Catch Dark Mode plugin if it is not essential. Monitor web server logs for suspicious include attempts or unusual PHP file accesses. Implement strict file upload restrictions to prevent unauthorized PHP file uploads, including disabling execution permissions in upload directories. Employ Web Application Firewalls (WAFs) with rules targeting LFI attack patterns to block exploitation attempts. Regularly audit user roles and permissions to ensure least privilege principles. Until an official patch is released, consider applying virtual patching through WAFs or custom code filters that sanitize or block the vulnerable shortcode usage. Keep WordPress core and all plugins updated and subscribe to vendor advisories for patch releases. Conduct penetration testing focused on file inclusion vulnerabilities to identify residual risks.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, France, Netherlands, India, Brazil, Japan
CVE-2025-10143: CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in catchthemes Catch Dark Mode
Description
The Catch Dark Mode plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.0 via the 'catch_dark_mode' shortcode. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary .php 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 .php file types can be uploaded and included.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-10143 is a Local File Inclusion vulnerability identified in the Catch Dark Mode plugin for WordPress, affecting all versions up to 2.0. The vulnerability arises from improper validation and control of filenames used in PHP include or require statements within the 'catch_dark_mode' shortcode functionality. An attacker with authenticated access at the Contributor role or higher can leverage this flaw to include arbitrary PHP files from the server filesystem. This inclusion leads to execution of any PHP code contained within those files, enabling a range of malicious activities such as bypassing WordPress access controls, reading sensitive configuration or user data, and executing arbitrary commands on the server. The attack vector requires network access and authenticated privileges but does not require user interaction. The CVSS 3.1 base score of 7.5 reflects high severity due to the potential for confidentiality, integrity, and availability impacts. Although no public exploits are currently known, the vulnerability represents a significant risk given the widespread use of WordPress and the Catch Dark Mode plugin. The root cause is classified under CWE-98, indicating improper control of filenames in include/require statements, a common source of LFI vulnerabilities. Without a patch available at the time of disclosure, mitigation relies on access control hardening and monitoring.
Potential Impact
The impact of CVE-2025-10143 is substantial for organizations running WordPress sites with the Catch Dark Mode plugin installed. Successful exploitation allows attackers to execute arbitrary PHP code on the web server, which can lead to full site compromise. This includes bypassing authentication and authorization controls, exposing sensitive user data, modifying website content, deploying web shells, or pivoting to other internal systems. The vulnerability affects the confidentiality, integrity, and availability of affected systems. Given that Contributor-level access is sufficient, attackers who gain low-privilege credentials or exploit other vulnerabilities to escalate privileges can leverage this flaw to gain full control. The lack of user interaction and network-based attack vector increases the risk of automated exploitation once details become public. Organizations may face reputational damage, data breaches, and service disruptions if this vulnerability is exploited.
Mitigation Recommendations
To mitigate CVE-2025-10143, organizations should immediately restrict Contributor and higher roles to trusted users only, minimizing the attack surface. Disable or remove the Catch Dark Mode plugin if it is not essential. Monitor web server logs for suspicious include attempts or unusual PHP file accesses. Implement strict file upload restrictions to prevent unauthorized PHP file uploads, including disabling execution permissions in upload directories. Employ Web Application Firewalls (WAFs) with rules targeting LFI attack patterns to block exploitation attempts. Regularly audit user roles and permissions to ensure least privilege principles. Until an official patch is released, consider applying virtual patching through WAFs or custom code filters that sanitize or block the vulnerable shortcode usage. Keep WordPress core and all plugins updated and subscribe to vendor advisories for patch releases. Conduct penetration testing focused on file inclusion vulnerabilities to identify residual risks.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-09-08T20:51:23.453Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68ca1a3d571b2840ff0172de
Added to database: 9/17/2025, 2:17:33 AM
Last enriched: 2/27/2026, 6:10:24 PM
Last updated: 3/26/2026, 7:04:58 AM
Views: 130
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.