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-14160: CWE-352 Cross-Site Request Forgery (CSRF) in justdave Upcoming for Calendly

0
Medium
VulnerabilityCVE-2025-14160cvecve-2025-14160cwe-352
Published: Fri Dec 12 2025 (12/12/2025, 03:20:58 UTC)
Source: CVE Database V5
Vendor/Project: justdave
Product: Upcoming for Calendly

Description

The Upcoming for Calendly plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2.4. This is due to missing nonce validation on the settings update functionality. This makes it possible for unauthenticated attackers to update the plugin's Calendly API key via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

AI-Powered Analysis

AILast updated: 12/12/2025, 04:04:30 UTC

Technical Analysis

CVE-2025-14160 is a Cross-Site Request Forgery (CSRF) vulnerability identified in the Upcoming for Calendly plugin for WordPress, affecting all versions up to and including 1.2.4. The root cause is the absence of nonce validation on the settings update endpoint, which is responsible for updating the plugin's Calendly API key. Nonces in WordPress are security tokens used to verify that requests are intentional and originate from legitimate users. Without nonce validation, attackers can craft malicious requests that, when executed by an authenticated administrator (via clicking a link or visiting a crafted webpage), cause unauthorized changes to the plugin's configuration. This can lead to integrity compromise by allowing attackers to replace the legitimate API key with one under their control, potentially redirecting scheduling data or manipulating booking workflows. The vulnerability does not require authentication from the attacker but does require user interaction by an administrator, limiting ease of exploitation. The CVSS v3.1 score is 4.3, with attack vector network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), user interaction required (UI:R), unchanged scope (S:U), no confidentiality impact (C:N), low integrity impact (I:L), and no availability impact (A:N). No patches or exploits are currently documented, but the risk remains for sites that have not updated or mitigated this issue. The vulnerability was published on December 12, 2025, and assigned by Wordfence.

Potential Impact

For European organizations, this vulnerability poses a moderate risk primarily to the integrity of their WordPress sites using the Upcoming for Calendly plugin. Unauthorized modification of the Calendly API key could allow attackers to hijack scheduling functionalities, potentially redirecting appointments or injecting malicious data into booking workflows. This could disrupt business operations, cause reputational damage, or lead to indirect data exposure if attackers manipulate scheduling communications. Since the exploit requires an administrator to interact with a malicious link, social engineering campaigns targeting site admins could be effective. Organizations relying heavily on online scheduling and customer interaction through WordPress sites are at higher risk. The impact on confidentiality and availability is minimal, but integrity compromise can have downstream effects on trust and operational continuity. Given the widespread use of WordPress across Europe and the popularity of scheduling tools, the threat is relevant to many sectors including SMEs, service providers, and public institutions.

Mitigation Recommendations

To mitigate CVE-2025-14160, organizations should immediately update the Upcoming for Calendly plugin to a patched version once available. In the absence of a patch, administrators should implement manual nonce validation on the settings update endpoint by modifying the plugin code to verify WordPress nonces before processing requests. Additionally, administrators should be trained to recognize and avoid clicking suspicious links, especially those that could trigger administrative actions. Employing Web Application Firewalls (WAFs) with custom rules to detect and block unauthorized POST requests to the plugin’s settings endpoint can provide temporary protection. Limiting administrative access to trusted networks and enforcing multi-factor authentication (MFA) for WordPress admin accounts reduces the risk of successful social engineering. Regular monitoring of plugin settings and API keys for unauthorized changes is also recommended. Finally, organizations should maintain an inventory of WordPress plugins and their versions to quickly identify vulnerable instances.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-05T20:39:55.897Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 693b918b650da22753edbe28

Added to database: 12/12/2025, 3:52:43 AM

Last enriched: 12/12/2025, 4:04:30 AM

Last updated: 12/15/2025, 4:03:39 AM

Views: 32

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats