CVE-2025-13973
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe StickEasy Protected Contact Form plugin for WordPress stores spam detection logs at a predictable, publicly accessible path (wp-content/uploads/stickeasy-protected-contact-form/spcf-log.txt). This allows unauthenticated attackers to directly download the log file and obtain sensitive visitor information including IP addresses, email addresses, and form submission content that was flagged as spam.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installationIn WordPress admin, go to Plugins > Installed Plugins and look for 'StickEasy Protected Contact Form' or check the wp-content/plugins directory for a folder named 'stickeasy-protected-contact-form'Affected if The plugin is installed and active
-
Check for vulnerable log file existenceAccess the URL path /wp-content/uploads/stickeasy-protected-contact-form/spcf-log.txt via a web browser or curl command: curl -I https://yourdomain.com/wp-content/uploads/stickeasy-protected-contact-form/spcf-log.txtAffected if The server returns HTTP 200 OK (file exists and is accessible)
-
Verify log file is publicly downloadableAttempt to download the file using: curl -o spcf-log.txt https://yourdomain.com/wp-content/uploads/stickeasy-protected-contact-form/spcf-log.txtAffected if The file downloads without requiring authentication or login
-
Inspect log contents for sensitive dataOpen the downloaded file and search for entries containing email addresses, IP addresses, or form submission data that was flagged as spamAffected if The log file contains any visitor IP addresses, email addresses, or form submission content
A user is affected if the StickEasy Protected Contact Form plugin is installed and the spcf-log.txt file exists and is publicly accessible at the predictable uploads path.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately delete or move the publicly accessible log file from the uploads directory, and implement web server access controls (e.g., .htaccess deny rules) on the stickeasy-protected-contact-form directory to prevent unauthorized access. Monitor for any signs of prior unauthorized access.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13973 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13973 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data