LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1072: Keybase.io Verification <= 1.4.5 - Cross-Site Request Forgery to Settings Update

The Keybase.io Verification plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.4.5. This is due to missing nonce validation when updating plugin settings. This makes it possible for unauthenticated attackers to update the Keybase verification text 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

This affects the Keybase.io Verification WordPress plugin through version 1.4.5. A malicious site or link could trick a logged-in administrator into changing the plugin’s Keybase verification text. The business impact is limited integrity risk, not data theft or service outage based on current sources.

Executive priority

Handle during normal vulnerability remediation unless the plugin supports an important identity or trust workflow. Prioritize exposed public WordPress sites with many administrators or weak admin browsing practices.

Technical view

CVE-2026-1072 is a CSRF flaw caused by missing nonce validation during plugin settings updates. An unauthenticated attacker needs administrator interaction to submit a forged request that updates Keybase verification text. CVSS 3.1 is 4.3, with network access, low complexity, no privileges, and required user interaction.

Likely exposure

WordPress sites running Keybase.io Verification plugin versions up to and including 1.4.5 are the relevant exposure. Sites without this plugin, or not using affected versions, are not indicated as exposed by the provided sources.

Exploitation context

No active exploitation is stated in the provided sources, and the CVE is not listed as KEV. Exploitation requires social engineering of a logged-in site administrator, such as convincing them to click a malicious link.

Researcher notes

Sources identify CWE-352 and missing nonce validation in the settings update path. The bundle references WordPress Trac source and a changeset, but does not clearly name a fixed release. Do not assume active exploitation or broader impact beyond settings integrity.

Mitigation direction

  • Inventory WordPress sites for the Keybase.io Verification plugin and its version.
  • Update the plugin if a patched version is available from WordPress or the vendor.
  • If no patch is available, consider disabling the plugin if not business-critical.
  • Warn administrators not to click untrusted links while logged into WordPress.
  • Review and reset the Keybase verification text if unexpected changes are found.

Validation and detection

  • Confirm whether the plugin is installed on each WordPress site.
  • Check whether the installed version is 1.4.5 or earlier.
  • Review plugin settings for unauthorized Keybase verification text changes.
  • Review the referenced WordPress Trac code and changeset for nonce validation status.
  • Monitor Wordfence, CVE, and WordPress plugin sources for updated remediation guidance.
Prepared
Confidence
medium
Sources
6

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-1072 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
5Source 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-1072Attack 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
jamesitsKeybase.io Verification0unaffected
Weakness

CWE details

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