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-47315: Cross-Site Request Forgery (CSRF) in StellarWP GiveWP

0
Unknown
VulnerabilityCVE-2024-47315cvecve-2024-47315
Published: Wed Sep 25 2024 (09/25/2024, 17:32:56 UTC)
Source: CVE Database V5
Vendor/Project: StellarWP
Product: GiveWP

Description

Cross-Site Request Forgery (CSRF) vulnerability in StellarWP GiveWP give.This issue affects GiveWP: from n/a through <= 3.15.1.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/02/2026, 05:57:56 UTC

Technical Analysis

CVE-2024-47315 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the StellarWP GiveWP plugin, a widely used WordPress plugin designed for managing donations. The vulnerability affects all versions up to and including 3.15.1. CSRF vulnerabilities occur when an attacker tricks an authenticated user into submitting a forged request to a web application, causing the application to perform unintended actions on behalf of the user. In this case, an attacker could craft a malicious web page or link that, when visited by a logged-in user with sufficient privileges in GiveWP, could trigger unauthorized actions such as modifying donation settings, altering payment information, or other administrative functions exposed by the plugin. The vulnerability does not require the attacker to have direct access to the victim’s credentials but relies on the victim being authenticated and visiting a malicious site. No CVSS score has been assigned yet, and no public exploits have been reported, but the vulnerability is publicly disclosed and should be considered a risk. The absence of patch links indicates that a fix may be pending or recently released. The vulnerability's technical details are limited, but the nature of CSRF implies that the plugin lacks proper anti-CSRF tokens or validation mechanisms on sensitive state-changing requests. This flaw can compromise the integrity and availability of donation management operations within affected WordPress sites.

Potential Impact

The impact of this CSRF vulnerability is significant for organizations relying on GiveWP for donation processing and management. An attacker exploiting this flaw could perform unauthorized actions such as changing donation amounts, redirecting funds, modifying payment gateways, or altering donor information without the victim's consent. This can lead to financial loss, reputational damage, and disruption of fundraising activities. Since GiveWP is often used by nonprofits, charities, and other organizations that depend on donations, the integrity and availability of their donation systems are critical. Additionally, unauthorized changes could result in compliance violations or loss of donor trust. The attack requires the victim to be authenticated, which limits the scope but still affects any logged-in administrative or privileged user. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers often develop exploits after public disclosure. Overall, the vulnerability could lead to unauthorized administrative actions, data manipulation, and potential denial of service within the donation platform.

Mitigation Recommendations

Organizations using GiveWP should immediately verify their plugin version and plan to upgrade to a patched version once available from StellarWP. In the interim, administrators should implement strict access controls to limit the number of users with administrative privileges. Employing web application firewalls (WAFs) that can detect and block CSRF attack patterns may provide temporary protection. Site owners should ensure that all sensitive actions require proper anti-CSRF tokens and verify the origin of requests. Additionally, educating users to avoid clicking on suspicious links while logged into administrative accounts can reduce risk. Monitoring logs for unusual administrative activity can help detect exploitation attempts. If custom code or integrations exist, review them to ensure they implement CSRF protections. Finally, maintain regular backups of donation data to enable recovery in case of compromise.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2024-09-24T13:00:24.006Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69cd748ee6bfc5ba1def7ef2

Added to database: 4/1/2026, 7:39:58 PM

Last enriched: 4/2/2026, 5:57:56 AM

Last updated: 4/6/2026, 9:32:04 AM

Views: 6

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 for AI refresh and higher limits.

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

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses