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-2024-13444: CWE-352 Cross-Site Request Forgery (CSRF) in tuxlog wp-greet

0
Medium
VulnerabilityCVE-2024-13444cvecve-2024-13444cwe-352
Published: Tue Jan 21 2025 (01/21/2025, 11:09:47 UTC)
Source: CVE Database V5
Vendor/Project: tuxlog
Product: wp-greet

Description

CVE-2024-13444 is a Cross-Site Request Forgery (CSRF) vulnerability in the wp-greet WordPress plugin by tuxlog, affecting all versions up to 6. 2. The flaw arises from missing or incorrect nonce validation, allowing unauthenticated attackers to trick site administrators into executing malicious actions such as updating settings or injecting scripts. Exploitation requires user interaction, specifically an administrator clicking a crafted link. The vulnerability has a CVSS score of 6. 1, indicating medium severity, with potential impacts on confidentiality and integrity but not availability. No known exploits are currently reported in the wild. Organizations using the wp-greet plugin should prioritize patching or applying mitigations to prevent unauthorized configuration changes and script injections. Countries with significant WordPress usage and large web hosting markets are most at risk.

AI-Powered Analysis

AILast updated: 02/26/2026, 00:58:59 UTC

Technical Analysis

CVE-2024-13444 is a medium-severity vulnerability classified under CWE-352 (Cross-Site Request Forgery) affecting the wp-greet plugin for WordPress, developed by tuxlog. The vulnerability exists in all versions up to and including 6.2 due to missing or incorrect nonce validation on a critical function within the plugin. Nonces in WordPress are security tokens used to verify that requests are intentional and originate from legitimate users. The absence or improper implementation of nonce validation allows unauthenticated attackers to craft malicious requests that, when executed by an authenticated administrator (via user interaction such as clicking a link), can update plugin settings or inject malicious web scripts. This can lead to unauthorized changes in site behavior and potential cross-site scripting (XSS) attacks. The vulnerability does not require prior authentication but does require user interaction, limiting automated exploitation. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) reflects network attack vector, low attack complexity, no privileges required, user interaction required, scope changed, and low impact on confidentiality and integrity, with no impact on availability. No patches or exploits are currently publicly available, but the vulnerability is published and should be addressed promptly.

Potential Impact

The primary impact of CVE-2024-13444 is on the confidentiality and integrity of affected WordPress sites using the wp-greet plugin. An attacker can manipulate plugin settings or inject malicious scripts by exploiting the CSRF flaw, potentially leading to unauthorized data exposure or site defacement. The injected scripts could facilitate further attacks such as session hijacking, phishing, or malware distribution. Although availability is not directly affected, the integrity compromise can undermine trust in the affected websites. Organizations relying on wp-greet for greeting or user interaction features may face reputational damage and increased risk of broader compromise if attackers leverage this vulnerability as an initial foothold. The requirement for administrator interaction reduces the likelihood of mass exploitation but does not eliminate targeted attacks against high-value sites. The vulnerability affects all versions up to 6.2, so unpatched sites remain at risk.

Mitigation Recommendations

To mitigate CVE-2024-13444, organizations should immediately verify if they use the wp-greet plugin and update to a patched version once available. In the absence of an official patch, administrators should consider disabling or removing the plugin to eliminate the attack surface. Implementing strict Content Security Policy (CSP) headers can help reduce the impact of injected scripts. Additionally, educating site administrators about the risks of clicking untrusted links can reduce the likelihood of successful exploitation. Site owners should also enable multi-factor authentication (MFA) for administrative accounts to limit the impact of compromised credentials. Monitoring web server and application logs for unusual requests or changes to plugin settings can help detect attempted exploitation. Finally, developers should ensure nonce validation is correctly implemented in all plugin functions that modify settings or perform sensitive actions.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-01-15T21:43:27.604Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6e57b7ef31ef0b59e917

Added to database: 2/25/2026, 9:49:11 PM

Last enriched: 2/26/2026, 12:58:59 AM

Last updated: 2/26/2026, 6:45:19 AM

Views: 1

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