Skip to main content

WPForms Database Addon EUVDEUVD-2026-94746

| CVE-2026-105260 MEDIUM
Cross-Site Request Forgery (CSRF) (CWE-352)
2026-10-08 contact@wpscan.com GHSA-rcvv-3xw8-xphv
4.3
CVSS 3.1 · Vendor: wpscan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Lure logged-in admin to crafted page
  2. Exploit
    Browser auto-submits forged delete request
  3. Execution
    Plugin skips nonce and capability checks
  4. Impact
    Stored form entries deleted

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V3 - Web Frontend Security Anti-CSRF tokens, SameSite cookies
MITRE ATT&CK

1 technique across 1 tactic: Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated WordPress administrator with an active session to be tricked (UI:R) into loading an attacker-controlled page while logged in; the vulnerable entry-deletion handler in Database Addon For WPForms before 1.1.1 does not validate the CSRF nonce when the field is omitted and performs no capability check, so no credentials or configuration changes are needed by the attacker. Limiting factors: the attack only succeeds against sites running this specific addon at a vulnerable version, depends on social-engineering a privileged user, and impact is confined to deletion of stored form entries (no confidentiality or availability loss, no code execution).

Impact

This is a CSRF flaw (CWE-352) with a vendor-assigned CVSS of 4.3 and an independently consistent vector of CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N - network-reachable and low-complexity, but gated on user interaction (UI:R) by a logged-in administrator and limited to integrity-only impact (C:N/I:L/A:N), which explains the Medium rather than High rating. No EPSS score, KEV listing, or public POC was provided in the input, so there is no signal of active or probable exploitation; exploitation status is therefore 'no public exploit identified at time of analysis.' No SSVC decision data was supplied. The realistic priority is moderate-to-low: the technical impact is bounded (deletion of stored form entries, not code execution or data disclosure), and successful attack requires social-engineering an authenticated admin into visiting a crafted page. One caveat: PR:N reflects that the attacker needs no credentials, but the attack still depends entirely on an administrator session, so the UI:R factor is the true limiting condition - raw 'network/unauthenticated' framing overstates reach. A patch is confirmed available, making remediation straightforward.

Exploit ScenarioDerived

An attacker crafts a malicious web page (or email link) containing a hidden request that triggers the plugin's entry-deletion action, which omits the CSRF nonce field and performs no capability check. When a logged-in WordPress administrator is lured into loading that page, their authenticated browser silently issues the delete request, removing arbitrary stored WPForms entries. No public exploit code is identified at time of analysis, but AC:L and the omitted nonce make the request trivial to forge.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 08, 2026

Deletion of stored form entries in the WordPress plugin Database Addon for WPForms (also distributed as 'wpforms entries') is possible against any site running a version before 1.1.1, because the entry-removal handler fails to validate a CSRF nonce when that field is omitted and performs no capability check of its own. An attacker can host a crafted page that, when loaded by a logged-in WordPress administrator, silently submits the deletion request on the victim's behalf; the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N confirms network reachability and low complexity but gates success on administrator interaction. Impact is integrity-only (C:N/I:L/A:N, CVSS 4.3 Medium) and limited to removal of stored form submissions, with no code execution, data disclosure, or site availability loss; there is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV).

RemediationAI

The primary fix is a vendor patch: update Database Addon For WPForms ('wpforms entries') to version 1.1.1 or later, which is the first release outside the affected range '0 <1.1.1' and restores nonce validation and/or capability checking on the entry-deletion handler; verify the installed version from the WordPress Plugins screen or with WP-CLI (wp plugin list --status=active) and confirm the update applied. Because the patch is confirmed available from the vendor, no compensating control should be treated as a substitute for upgrading. If the update cannot be applied immediately, the effective interim measures are to deactivate the addon (the entry-management UI and its delete action disappear, at the cost of losing access to stored WPForms entries until it is re-enabled) or, if the plugin must stay active, restrict who can be socially engineered into triggering the forged request - administrators should keep a separate browser profile or log out of wp-admin when browsing untrusted sites, and outbound navigation from the admin session should be treated as hostile. A targeted mu-plugin or theme-level filter that re-registers or short-circuits the addon's delete-entry action with an explicit wp_verify_nonce() and current_user_can() check can neutralise the flaw without waiting for the release, but such custom code must be validated against the plugin's actual action name and hook signature or it will either leave the flaw open or break legitimate entry deletion. Applying a web application firewall CSRF rule set offers marginal value here since the forged request originates from the victim's own browser and carries valid session cookies; it should not be counted on. No vendor-released workaround other than the 1.1.1 update is documented in the supplied advisory.

Affected VersionsENISA

Database Addon For WPForms ( wpforms entries ) 0 <1.1.1

Affected Packages

euvd database_addon_for_wpforms_wpforms_entries fix: 1.1.1

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is a WordPress plugin that stores WPForms submission data in custom database tables and exposes administrative entry-management actions. Root cause is CWE-352 (Cross-Site Request Forgery): the plugin's delete-entry request handler relies on a WordPress nonce for request authenticity, but that validation is skipped entirely when the nonce parameter is absent from the request, and the handler does not perform its own current_user_can() capability check to compensate. In WordPress, nonces bound the request to the current session and user; omitting the field generally causes wp_verify_nonce() to fail, but here the missing-field branch bypasses the check, so a forged request carrying only an entry identifier is accepted. Because no capability check is enforced in the handler, the request is honoured on the strength of the victim administrator's existing session cookie alone. This is the classic pairing of two missing controls (nonce + authorization) rather than a memory-safety or injection defect, which is why the impact is confined to unauthorized deletion of records. Affected distribution per EUVD is the 'Database Addon For WPForms ( wpforms entries )' plugin at versions 0 through <1.1.1; the upstream advisory is WPScan entry 532d21c1-448f-422d-8d58-a76e9cff99e4, cross-referenced under EUVD-2026-94746.

Know when WordPress gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (wpscan) PRIMARY 4.3 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
vuln.today AI 4.3 MEDIUM

Attacker needs no privileges (PR:N) but must trick a logged-in admin (UI:R); forging the nonce-less request is trivial (AC:L); impact is limited to entry deletion (I:L, C/A:N).

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (wpscan).

CVSS VectorVendor: wpscan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

Lifecycle Timeline

4
CVSS changed
Oct 08, 2026 - 11:22 NVD
4.3 (MEDIUM)
Patch available
Oct 08, 2026 - 07:01 EUVD
CVE Published
Oct 08, 2026 - 06:16 cve.org
UNKNOWN (no severity yet)
CVE Published
Oct 08, 2026 - 06:16 cve.org
MEDIUM 4.3

DescriptionCVE.org

The Database Addon For WPForms ( wpforms entries ) WordPress plugin before 1.1.1 does not verify the CSRF nonce when the field is omitted and performs no capability check of its own, allowing attackers to delete arbitrary stored form entries by tricking a logged-in administrator into loading a crafted page.

Threat Intelligence Overview

EPSS Score
0.1%
Top 99% exploitable
Prevalence
Low
niche third-party addon extending WPForms, limited install base
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

22
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +22
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.

CVE-2016-10033 CRITICAL POC
9.8 Dec 30

The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para

CVE-2016-10045 CRITICAL POC
9.8 Dec 30

The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

CVE-2024-5084 CRITICAL POC
9.8 May 23

The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil

CVE-2024-44000 CRITICAL POC
9.8 Oct 20

Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote

CVE-2024-8353 CRITICAL POC
9.8 Sep 28

The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all

CVE-2020-36847 CRITICAL POC
9.8 Jul 12

The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner

CVE-2025-11749 CRITICAL POC
9.8 Nov 05

The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint

CVE-2025-27007 CRITICAL POC
9.8 May 01

The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut

CVE-2016-1209 CRITICAL POC
9.8 May 14

The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via

CVE-2024-4443 CRITICAL POC
9.8 May 22

The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based

CVE-2026-63030 CRITICAL POC
9.8 Jul 17

Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy