CVE-2026-18946

Contact Form to Any API <= 3.0.6 - Unauthenticated Sensitive File Disclosure

2026-08-06 00:00
Farid Narimanov

Strategic Overview

Status
Patched in 3.0.7
Affected Plugin
Contact Form to Any API
Affected Version
<= 3.0.6
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-18946
View all Contact Form to Any API vulnerabilities

At a glance

CVE-2026-18946 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Contact Form to Any API WordPress plugin, affecting versions <= 3.0.6. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.0.7; sites on affected versions should update now. Disclosed August 2026, reported by Farid Narimanov.

Vulnerability Overview

The Contact Form to Any API plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 3.0.6. This is due to use of a predictable filename pattern (form_id + timestamp) for uploaded files stored in a publicly accessible directory, allowing unauthenticated enumeration and direct retrieval. This makes it possible for unauthenticated attackers to access uploaded form submission files by guessing their predictable filenames, which were constructed from a known form ID and Unix timestamp.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Contact Form to Any API <= 3.0.6 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Contact Form to Any API the fix is 3.0.7: builds <= 3.0.6 are affected, anything from 3.0.7 onward is not.

Remediation

Update to version 3.0.7, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Contact Form to Any API 3.0.7 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-18946https://www.wordfence.com/threat-intel/vulnerabilities/id/0ae1cfe2-db79-46ba-bf10-0ee47f98e204https://nvd.nist.gov/vuln/detail/CVE-2026-18946

Related records

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