Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13748: CWE-639 Authorization Bypass Through User-Controlled Key in techjewel Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder

0
Medium
VulnerabilityCVE-2025-13748cvecve-2025-13748cwe-639
Published: Sat Dec 06 2025 (12/06/2025, 06:39:08 UTC)
Source: CVE Database V5
Vendor/Project: techjewel
Product: Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder

Description

The Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 6.1.7 via the 'submission_id' parameter due to missing validation on a user controlled key within the confirmScaPayment() function. This makes it possible for unauthenticated attackers to mark arbitrary submissions as failed via crafted requests to the endpoint granted they can guess or enumerate a valid submission identifier.

AI-Powered Analysis

AILast updated: 12/13/2025, 07:08:31 UTC

Technical Analysis

CVE-2025-13748 is an authorization bypass vulnerability classified under CWE-639 (Authorization Bypass Through User-Controlled Key) affecting the Fluent Forms – Customizable Contact Forms, Survey, Quiz, & Conversational Form Builder WordPress plugin by techjewel. The vulnerability exists in all versions up to and including 6.1.7 within the confirmScaPayment() function, where the 'submission_id' parameter is accepted from user input without proper validation. This parameter is used to identify form submissions, and due to the lack of authorization checks, an unauthenticated attacker can craft requests to the vulnerable endpoint to mark arbitrary submissions as failed. The attack surface is remote and requires no authentication or user interaction, relying on the ability to guess or enumerate valid submission IDs. While the vulnerability does not expose sensitive data or cause denial of service, it compromises the integrity of submission records by allowing unauthorized modification of their status. The CVSS v3.1 base score is 5.3 (medium), reflecting the ease of exploitation and limited impact scope. No patches were linked at the time of publication, and no exploits have been observed in the wild. The vulnerability is significant for organizations relying on Fluent Forms for critical data collection, as it could disrupt workflows, cause confusion, or be leveraged as part of a larger attack chain.

Potential Impact

For European organizations, the primary impact of CVE-2025-13748 is the integrity compromise of form submission data within websites using the Fluent Forms plugin. This could lead to business process disruptions, such as lost or misrepresented survey results, contact requests, or quiz outcomes. While confidentiality and availability remain unaffected, the ability for unauthenticated attackers to alter submission statuses could undermine trust in data accuracy and potentially affect decision-making processes based on form inputs. Organizations in sectors like e-commerce, customer service, education, and public administration that rely heavily on online forms may experience operational inefficiencies or reputational damage. Additionally, attackers could use this vulnerability as a foothold to probe for further weaknesses or to disrupt user interactions. The lack of authentication and user interaction requirements increases the risk of automated exploitation attempts, especially if submission IDs are predictable or enumerable.

Mitigation Recommendations

1. Monitor for updates from techjewel and apply security patches for Fluent Forms promptly once released. 2. Implement web application firewall (WAF) rules to restrict access to the confirmScaPayment() endpoint, limiting requests to trusted IPs or authenticated users where possible. 3. Employ rate limiting and anomaly detection to prevent enumeration or brute force attempts on submission IDs. 4. Review and harden the plugin’s configuration to minimize exposure of sensitive endpoints. 5. Conduct regular audits of form submission logs to detect unauthorized status changes. 6. Consider temporary disabling or replacing the plugin if immediate patching is not feasible and the risk is unacceptable. 7. Educate site administrators on the risks and signs of exploitation to enable rapid response. 8. Use security plugins or services that can detect and block suspicious HTTP requests targeting vulnerable parameters.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-26T15:56:07.294Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6933d18711163305effc5a0e

Added to database: 12/6/2025, 6:47:35 AM

Last enriched: 12/13/2025, 7:08:31 AM

Last updated: 1/20/2026, 10:09:43 AM

Views: 98

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats