LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1380: Bitcoin Donate Button <= 1.0 - Cross-Site Request Forgery to Settings Update

The Bitcoin Donate Button plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. This is due to missing or incorrect nonce validation on the settings page. This makes it possible for unauthenticated attackers to modify the plugin's settings, including donation addresses and display configurations, via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A WordPress plugin used to display Bitcoin donation buttons can have its settings changed if an administrator is tricked into taking an action. An attacker could potentially replace donation addresses or alter display settings. This is not reported as actively exploited, but it creates a business risk of misdirected donations and site integrity loss.

Executive priority

Treat as a moderate-priority website integrity issue. Prioritize sites receiving donations or using this plugin on public-facing WordPress installations. Remediate during the next maintenance window unless suspicious settings changes are found.

Technical view

CVE-2026-1380 is a CSRF vulnerability in Bitcoin Donate Button for WordPress, reported in versions up to and including 1.0. The settings page lacks proper nonce validation. The CVSS 3.1 score is 4.3, reflecting network reachability, no attacker privileges, required user interaction, and low integrity impact.

Likely exposure

Exposure is limited to WordPress sites with the Bitcoin Donate Button plugin installed at version 1.0 or earlier. The main risk is unauthorized plugin settings modification after administrator interaction.

Exploitation context

The attacker must convince a logged-in site administrator to perform an action such as clicking a link. The provided sources do not show active exploitation, public weaponization, or KEV listing.

Researcher notes

Sources identify CWE-352 CSRF caused by missing or incorrect nonce validation on the settings page. The provided bundle does not name a fixed version or vendor patch. Affected-version metadata is inconsistent, so verify against the Wordfence entry and WordPress plugin repository.

Mitigation direction

  • Check vendor or WordPress plugin guidance for an updated fixed release.
  • If no fixed release is available, deactivate and remove the plugin if not essential.
  • Review plugin donation addresses and display settings for unauthorized changes.
  • Train administrators to avoid unsolicited links while logged into WordPress.

Validation and detection

  • Inventory WordPress sites for the Bitcoin Donate Button plugin.
  • Confirm installed plugin version is 1.0 or earlier.
  • Review current donation address and display configuration values.
  • Check WordPress administrative activity logs for unexpected settings changes.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
cve · low confidence lookup

CVE-2026-1380 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-1380Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
lxiconBitcoin Donate Button0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

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.