Skip to main content
DashboardThreatsMapFeedsAPI
reconnecting
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-60117: CWE-352 Cross-Site Request Forgery (CSRF) in TangibleWP Vehica Core

0
Medium
VulnerabilityCVE-2025-60117cvecve-2025-60117cwe-352
Published: Fri Sep 26 2025 (09/26/2025, 08:31:34 UTC)
Source: CVE Database V5
Vendor/Project: TangibleWP
Product: Vehica Core

Description

Cross-Site Request Forgery (CSRF) vulnerability in TangibleWP Vehica Core allows Cross Site Request Forgery. This issue affects Vehica Core: from n/a through 1.0.100.

AI-Powered Analysis

AILast updated: 09/27/2025, 00:14:16 UTC

Technical Analysis

CVE-2025-60117 is a Cross-Site Request Forgery (CSRF) vulnerability identified in the TangibleWP Vehica Core plugin, affecting versions up to 1.0.100. CSRF vulnerabilities occur when an attacker tricks an authenticated user into submitting a malicious request to a web application in which they are currently authenticated, thereby performing unwanted actions without the user's consent. In this case, the vulnerability allows attackers to craft malicious web requests that, when executed by an authenticated user, can cause unauthorized state-changing operations within the Vehica Core plugin environment. The CVSS 3.1 base score of 4.3 reflects a medium severity, indicating that while the vulnerability does not directly compromise confidentiality or availability, it can impact the integrity of the system by enabling unauthorized modifications. The attack vector is network-based (AV:N), requiring no privileges (PR:N), but does require user interaction (UI:R), meaning the victim must be tricked into clicking a malicious link or visiting a crafted webpage. The vulnerability does not require elevated privileges and affects the plugin's integrity without impacting confidentiality or availability. No known exploits are currently reported in the wild, and no patches have been published yet. The vulnerability is categorized under CWE-352, which is a common web application security weakness related to CSRF attacks. Given the plugin's role in WordPress environments, this vulnerability could be exploited to perform unauthorized actions such as changing settings or data within the Vehica Core plugin context, potentially leading to further compromise if chained with other vulnerabilities.

Potential Impact

For European organizations using the TangibleWP Vehica Core plugin, this vulnerability poses a risk primarily to the integrity of their web applications. Since Vehica Core is a WordPress plugin often used for real estate or listing websites, unauthorized changes could disrupt business operations, deface websites, or manipulate listings, potentially damaging reputation and trust. Although the vulnerability does not directly expose sensitive data or cause denial of service, attackers could leverage it to alter critical configurations or content, which might indirectly lead to data exposure or further exploitation. The requirement for user interaction limits the attack scope somewhat, but targeted phishing or social engineering campaigns could still be effective. Organizations with public-facing WordPress sites using this plugin are at risk, especially if users with administrative or privileged access are targeted. The absence of a patch increases exposure time, making timely mitigation essential. Additionally, the impact on integrity could have regulatory implications under European data protection laws if unauthorized changes lead to data mishandling or breaches.

Mitigation Recommendations

European organizations should implement several specific measures to mitigate this CSRF vulnerability in Vehica Core: 1) Immediately audit all WordPress sites using the Vehica Core plugin to identify affected versions (up to 1.0.100). 2) Until an official patch is released, apply Web Application Firewall (WAF) rules to detect and block suspicious CSRF attempts targeting plugin-specific endpoints. 3) Enforce strict Content Security Policy (CSP) headers and SameSite cookie attributes to reduce the risk of CSRF exploitation via cross-origin requests. 4) Educate users, especially administrators, about the risks of clicking untrusted links or visiting unknown websites while authenticated to WordPress admin panels. 5) Limit administrative access and enforce multi-factor authentication (MFA) to reduce the impact of successful CSRF attacks. 6) Monitor logs for unusual POST requests or changes in plugin settings that could indicate exploitation attempts. 7) Coordinate with TangibleWP for timely updates and apply patches as soon as they become available. 8) Consider temporarily disabling or restricting the plugin's functionality if feasible until a fix is deployed.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Patchstack
Date Reserved
2025-09-25T15:20:22.597Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68d72b6179aa5c9d0854f47a

Added to database: 9/27/2025, 12:10:09 AM

Last enriched: 9/27/2025, 12:14:16 AM

Last updated: 10/7/2025, 1:52:05 PM

Views: 8

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 are available only with a Pro account. Contact root@offseq.com for access.

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