CVE-2026-75799

YAHMAN · YAHMAN Add-ons WordPress plugin

The YAHMAN Add-ons WordPress plugin fails to validate remote files cached in a public directory, enabling unauthenticated remote code execution via arbitrary PHP file uploads.

Executive summary

An unauthenticated remote code execution vulnerability in the YAHMAN Add-ons WordPress plugin presents a critical risk to server integrity and data confidentiality.

Vulnerability

This flaw stems from improper validation of cached remote files, allowing an unauthenticated attacker to inject and execute arbitrary PHP code on the underlying server. The vulnerability is triggered when the specific caching feature is active.

Business impact

Successful exploitation grants an attacker full control over the web server, leading to potential data exfiltration, total system compromise, and the deployment of persistent backdoors. With a CVSS score of 9.0, this vulnerability is classified as critical due to the potential for complete loss of confidentiality, integrity, and availability.

Remediation

Immediate Action: Update the YAHMAN Add-ons plugin to version 0.9.31 or later immediately to resolve the file validation flaw.

Proactive Monitoring: Review web server access logs for suspicious requests targeting the plugin's caching directory or unexpected file execution patterns.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block unauthorized file uploads and prevent direct access to known plugin cache directories.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

Given the critical severity of this vulnerability and the potential for full system compromise, administrators must prioritize updating the YAHMAN Add-ons plugin to version 0.9.31. Organizations that cannot update immediately should disable the vulnerable caching feature or remove the plugin until a patch is applied to neutralize the risk of unauthorized code execution.

History

CVE Brief tracked this CVE 1 day before it had a CVSS score.

  1. Disclosed CVE record published
  2. Collected by CVE Brief No CVSS score yet; tracked as early warning
  3. CVSS score assigned 9.0 (3.1) from cvelistV5
  4. Analyst report written

Sources

Originally found and disclosed by Artus KG, with WPScan (coordinator), per the CVE Program record.