Cyber Resilience

CVE-2025-1128

Wpeverest Everest Forms ≤ 3.0.9.5

Published
25 February 2025
Modified
28 February 2025
Patch / advisory
View advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.29 98th percentile
Risk Priority 86 floored blend · peak EPSS

Summary

CVE-2025-1128 is a critical-severity Unrestricted Upload of File with Dangerous Type (CWE-434) vulnerability in Wpeverest Everest Forms. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-3 (Malicious Code Protection) and CM-7 (Least Functionality) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

The Everest Forms plugin for WordPress, which provides contact form, quiz, survey, and payment capabilities, contains an arbitrary file upload, read, and deletion flaw in all versions through 3.0.9.4. The root cause is missing file-type and path validation inside the format method of the EVF_Form_Fields_Upload class, allowing an attacker to supply arbitrary paths and extensions when handling form uploads.

Unauthenticated remote attackers can exploit the issue over the network to upload, read, or delete any file on the server. Successful abuse can result in remote code execution, disclosure of sensitive data such as configuration files or database credentials, or complete site takeover, consistent with the CVSS 9.8 rating.

Public references point to patches that add proper validation and restrict allowed file operations; the fixes appear in commit 7d37858 and subsequent WordPress.org plugin changesets that update the affected class. Site operators should upgrade to a version newer than 3.0.9.4 and verify that file-upload directories remain outside the web root.

The associated EPSS score has remained flat at 0.1144 with no material increase after disclosure.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

The Everest Forms – Contact Forms, Quiz, Survey, Newsletter & Payment Form Builder for WordPress plugin for WordPress is vulnerable to arbitrary file upload, read, and deletion due to missing file type and path validation in the 'format' method of…

more

the EVF_Form_Fields_Upload class in all versions up to, and including, 3.0.9.4. This makes it possible for unauthenticated attackers to upload, read, and delete arbitrary files on the affected site's server which may make remote code execution, sensitive information disclosure, or a site takeover possible.

CWE(s)
CWE-434

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1505 Server Software Component Persistence
Adversaries may abuse legitimate extensible development features of servers to establish persistent access to systems.
attack.mitre.org →
T1505.003 Web Shell Persistence
Adversaries may backdoor web servers with web shells to establish persistent access to systems.
attack.mitre.org →
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1105 Ingress Tool Transfer Command And Control
Adversaries may transfer tools or other files from an external system into a compromised environment.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-5927Same product: Wpeverest Everest Forms
CVE-2024-1812Same product: Wpeverest Everest Forms
CVE-2025-3439Same product: Wpeverest Everest Forms
CVE-2025-3422Same product: Wpeverest Everest Forms
CVE-2023-51377Same product: Wpeverest Everest Forms
CVE-2025-26841Same product: Wpeverest Everest Forms
CVE-2024-10471Same product: Wpeverest Everest Forms
CVE-2025-3421Same product: Wpeverest Everest Forms
CVE-2024-13125Same product: Wpeverest Everest Forms
CVE-2023-51695Same product: Wpeverest Everest Forms

Affected Assets

wpeverest
everest forms
≤ 3.0.9.5

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.1.1

Mitigating Controls (NIST 800-53 r5) AI

SI-3 Malicious Code Protection good match

Malicious-code protection at entry points blocks dangerous file types from being accepted and executed.

CM-7 Least Functionality partial match

Least functionality restricts the file types and automatic processing capabilities the system will accept.

SC-18 Mobile Code partial match

Mobile-code controls define, authorize, and block unacceptable uploaded code before automatic processing occurs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-05 mostly match
prevents

Restricting execution of unauthorized software directly blocks dangerous uploaded files from running.

PR.PS-01 partial match
prevents

Hardened configuration baselines can enforce allowed file types and processing rules.

PR.PS-06 partial match
prevents

Secure development practices include input validation and file-type restrictions that prevent this weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Configuration and acceptance testing verify that file-upload handling enforces allowed types and does not permit dangerous content to be stored or executed.

A.8.25 Secure development life cycle partial match
prevents

Secure-coding guidelines and security testing explicitly address restrictions on allowed file types and upload handling, reducing the risk that dangerous file uploads are accepted without validation.

A.8.30 Outsourced development partial match
prevents

Mandated testing for malicious content and known vulnerabilities reduces the likelihood that an outsourced component will contain or accept dangerous file types that could later be uploaded or executed.

A.8.7 Protection against malware partial match
mitigates

Application allow-listing and pre-use scanning of received files directly blocks the introduction of executable content that has not been vetted, eliminating the primary vector for unrestricted dangerous file uploads.

References