Security readout for executives and security teams
Plain-English summary
CVE-2026-1073 affects the WordPress plugin Purchase Button For Affiliate Link. A malicious site or link could trick a logged-in site administrator into changing the plugin’s settings. This requires administrator interaction, but could affect affiliate button behavior or related site configuration.
Executive priority
Treat as a moderate-priority WordPress plugin issue. It is not shown as actively exploited, but affected sites should be inventoried and remediated because administrator interaction can still lead to unauthorized setting changes.
Technical view
The issue is cross-site request forgery caused by missing nonce validation in the plugin settings page form handler at inc/purchase-btn-options-page.php. The CVE description states all versions up to and including 1.0.2 are vulnerable. CVSS is 4.3, with network attack vector, low complexity, no privileges, and required user interaction.
Likely exposure
Exposure is limited to WordPress sites running Purchase Button For Affiliate Link version 1.0.2 or earlier, especially where administrators browse while authenticated. Sites not using this plugin are not exposed.
Exploitation context
No CISA KEV listing is provided, and the source bundle does not cite active exploitation. Exploitation requires convincing a logged-in administrator to perform an action such as clicking a crafted link.
Researcher notes
The affected-version metadata in the bundle is inconsistent, but the CVE description clearly states all versions up to and including 1.0.2. Public references point to the settings page handler source. No patch version is identified in the provided sources.
Mitigation direction
- Identify WordPress sites using Purchase Button For Affiliate Link.
- Check vendor or Wordfence guidance for a fixed version or official remediation.
- If no fix is available, disable the plugin if it is not business-critical.
- Limit administrator browsing while logged into WordPress.
- Review plugin settings for unexpected changes.
Validation and detection
- Confirm whether the plugin is installed on each WordPress site.
- Record installed plugin versions and flag versions 1.0.2 or earlier.
- Verify whether vendor guidance identifies a patched release.
- Review plugin settings for unauthorized or unexpected values.
- Monitor administrative activity around plugin settings changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-1073 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/8c9a223c-6c34-4c64-92b5-d986f9791ebb?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/purchase-button/trunk/inc/purchase-btn-options-page.php#L3CVE reference
- https://plugins.trac.wordpress.org/browser/purchase-button/tags/1.0.2/inc/purchase-btn-options-page.php#L3CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.