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-22552: Cross-Site Request Forgery (CSRF) in bnielsen Affiliate Disclosure Statement

0
Unknown
VulnerabilityCVE-2025-22552cvecve-2025-22552
Published: Tue Jan 07 2025 (01/07/2025, 14:57:17 UTC)
Source: CVE Database V5
Vendor/Project: bnielsen
Product: Affiliate Disclosure Statement

Description

Cross-Site Request Forgery (CSRF) vulnerability in bnielsen Affiliate Disclosure Statement affiliate-disclosure-statement allows Cross Site Request Forgery.This issue affects Affiliate Disclosure Statement: from n/a through <= 0.3.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/02/2026, 01:26:40 UTC

Technical Analysis

CVE-2025-22552 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the bnielsen Affiliate Disclosure Statement plugin, specifically affecting versions up to 0.3. 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, the plugin lacks proper CSRF protections, such as anti-CSRF tokens, allowing malicious actors to craft requests that can be executed by logged-in users without their knowledge. This vulnerability could be exploited to manipulate affiliate disclosure statements or related settings, potentially misleading users or violating compliance requirements. Although no public exploits have been observed, the vulnerability is significant because it targets authenticated users, which may include administrators or content managers. The absence of a CVSS score indicates that the vulnerability is newly published and not yet fully assessed, but the technical details confirm the issue is recognized and documented by Patchstack. The vulnerability affects the bnielsen Affiliate Disclosure Statement plugin, a tool commonly used in WordPress environments to manage affiliate disclosures, which is critical for transparency and regulatory compliance in affiliate marketing. The affected versions are up to and including 0.3, with no patch links currently available, indicating that users should monitor vendor updates closely.

Potential Impact

The primary impact of this CSRF vulnerability is the potential unauthorized modification of affiliate disclosure statements or related plugin settings by attackers leveraging authenticated user sessions. This can lead to integrity issues where disclosures are altered or removed, potentially causing legal and compliance risks for organizations relying on accurate affiliate disclosures. Confidentiality may also be indirectly affected if attackers use the vulnerability to manipulate content that reveals sensitive affiliate relationships. Availability impact is minimal as the vulnerability does not directly cause denial of service. However, the trustworthiness of the website content can be compromised, affecting user confidence and brand reputation. Organizations with active affiliate marketing programs or regulatory obligations around disclosures are at higher risk. The vulnerability's exploitation requires the victim to be authenticated and visit a malicious site or click a crafted link, which is a moderate barrier but still feasible in targeted attacks. The lack of known exploits in the wild suggests limited current threat but does not preclude future exploitation once the vulnerability becomes widely known.

Mitigation Recommendations

To mitigate this vulnerability, organizations should implement robust anti-CSRF protections in the bnielsen Affiliate Disclosure Statement plugin, such as including unique CSRF tokens in forms and verifying them on the server side. Until an official patch is released, administrators should restrict plugin access to trusted users only and minimize the number of users with administrative or content editing privileges. Monitoring and logging changes to affiliate disclosure statements can help detect unauthorized modifications. Additionally, educating users about the risks of clicking unknown links while authenticated can reduce the likelihood of successful CSRF attacks. Organizations should subscribe to vendor notifications and apply updates promptly once patches become available. If feasible, temporarily disabling the plugin or replacing it with an alternative solution that follows secure coding practices may be warranted. Web application firewalls (WAFs) can also be configured to detect and block suspicious cross-site requests targeting the plugin endpoints.

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
2025-01-07T10:23:17.403Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69cd75f4e6bfc5ba1df088b3

Added to database: 4/1/2026, 7:45:56 PM

Last enriched: 4/2/2026, 1:26:40 AM

Last updated: 4/4/2026, 8:16:56 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 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