CVE-2026-1073
Received Received - Intake
CSRF Vulnerability in Purchase Button For Affiliate Link Plugin

Publication date: 2026-03-07

Last updated on: 2026-03-07

Assigner: Wordfence

Description
The Purchase Button For Affiliate Link plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.2. This is due to missing nonce validation on the settings page form handler in `inc/purchase-btn-options-page.php`. This makes it possible for unauthenticated attackers to modify plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-07
Last Modified
2026-03-07
Generated
2026-05-06
AI Q&A
2026-03-07
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The Purchase Button For Affiliate Link plugin for WordPress is vulnerable to a Cross-Site Request Forgery (CSRF) attack in all versions up to and including 1.0.2. This vulnerability exists because the plugin's settings page form handler in the file `inc/purchase-btn-options-page.php` lacks nonce validation, which is a security measure to verify that requests are legitimate.

As a result, an unauthenticated attacker can trick a site administrator into performing an action, such as clicking a malicious link, which then allows the attacker to modify the plugin's settings without proper authorization.


How can this vulnerability impact me? :

This vulnerability can allow an attacker to change the settings of the Purchase Button plugin on your WordPress site without your consent. Since the attacker can modify plugin options by tricking an administrator into clicking a crafted link, it could lead to unauthorized changes in how the purchase button behaves or appears.

While the vulnerability does not directly compromise confidentiality or availability (CVSS impact: No confidentiality or availability impact, low integrity impact), it can still undermine the integrity of your site’s configuration and potentially be used as a stepping stone for further attacks or to mislead users.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

[{'type': 'paragraph', 'content': "This vulnerability involves Cross-Site Request Forgery (CSRF) in the Purchase Button For Affiliate Link WordPress plugin, specifically due to missing nonce validation on the settings page form handler. Detection would involve monitoring for unauthorized or forged POST requests to the plugin's settings page that modify plugin options without proper authentication."}, {'type': 'paragraph', 'content': "Since the vulnerability is in the form submission handler in the file `inc/purchase-btn-options-page.php`, you can detect suspicious POST requests to the WordPress admin URL that includes this plugin's settings page."}, {'type': 'paragraph', 'content': 'Suggested commands to detect potential exploitation attempts include:'}, {'type': 'list_item', 'content': 'Using web server logs (e.g., Apache or Nginx) to search for POST requests to the plugin settings page URL.'}, {'type': 'list_item', 'content': 'Example command to search Apache logs for POST requests to the purchase button options page (adjust path as needed):'}, {'type': 'list_item', 'content': "grep 'POST' /var/log/apache2/access.log | grep 'purchase-btn-options-page.php'"}, {'type': 'list_item', 'content': 'Using WordPress security or activity logging plugins to monitor changes to plugin options or settings.'}, {'type': 'list_item', 'content': 'Monitoring for unexpected changes in the plugin options via database queries, for example, querying the WordPress options table for changes to keys related to the purchase button plugin.'}] [2, 3]


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, the primary step is to update the Purchase Button For Affiliate Link plugin to a version that includes proper nonce validation on the settings page form handler, if such an update is available.

If an update is not yet available, immediate mitigation steps include:

  • Restrict access to the WordPress admin area to trusted users only.
  • Implement additional security measures such as Web Application Firewalls (WAF) to block unauthorized POST requests to the plugin settings page.
  • Educate site administrators to avoid clicking on suspicious links that could trigger forged requests.
  • Manually patch the plugin code by adding nonce verification to the form handler in `inc/purchase-btn-options-page.php` to ensure requests are legitimate.

Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart