StickEasy Protected Contact Form <= 1.0.1 - Unauthenticated Information Disclosure
Strategic Overview
- Status
- Patched in 1.0.2
- Affected Plugin
- StickEasy Protected Contact Form
- Affected Version
<= 1.0.1- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2025-13973
At a glance
CVE-2025-13973 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the StickEasy Protected Contact Form WordPress plugin, affecting versions <= 1.0.1. 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 1.0.2; sites on affected versions should update now. Disclosed February 2026, reported by Itthidej Aramsri (Boeing777).
Vulnerability Overview
The StickEasy Protected Contact Form plugin for WordPress is vulnerable to Sensitive Information Disclosure in all versions up to, and including, 1.0.2. The plugin stores spam detection logs at a predictable publicly accessible location (wp-content/uploads/stickeasy-protected-contact-form/spcf-log.txt). This makes it possible for unauthenticated attackers to download the log file and access sensitive information including visitor IP addresses, email addresses, and comment snippets from contact form submissions that were flagged as spam.
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 StickEasy Protected Contact Form <= 1.0.1 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 StickEasy Protected Contact Form the fix is 1.0.2: builds <= 1.0.1 are affected, anything from 1.0.2 onward is not.
Remediation
Update to version 1.0.2, 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: StickEasy Protected Contact Form 1.0.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C