CVE-2026-73348Network attack vectorHinoki check available

Donor account takeover via unverified registration

Published Aug 18, 2026 · Updated Aug 18, 2026

Missing authorization in GiveWP before 4.16.6 allows remote attackers to access or rebind donor-linked accounts via front-end registration. Patchstack does not publish the exact function name, but the 4.16.6 security diff adds a registration nonce and only auto-links donor records to WordPress users when the data is marked as coming from the verified donation-checkout flow, indicating that earlier code accepted direct registration requests and linked donors by email without that gate. Exposure depends on sites that expose GiveWP registration, and the bounded impact is unauthorized visibility into a victim donor's history plus unauthorized reassignment of the donor-to-user association.

CVSS severity6.5
Medium
EPSS probability0.19%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Missing authorization in GiveWP before 4.16.6 allows remote attackers to access or rebind donor-linked accounts via front-end registration. Patchstack does not publish the exact function name, but the 4.16.6 security diff adds a registration nonce and only auto-links donor records to WordPress users when the data is marked as coming from the verified donation-checkout flow, indicating that earlier code accepted direct registration requests and linked donors by email without that gate. Exposure depends on sites that expose GiveWP registration, and the bounded impact is unauthorized visibility into a victim donor's history plus unauthorized reassignment of the donor-to-user association.

The record

CVE
CVE-2026-73348
Published
Aug 18, 2026
Updated
Aug 18, 2026
Vendor
The Events Calendar
Product
GiveWP
Classifications
CWE-862
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 18, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 18, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=n/a <4.16.6 changes=[{"at":"4.16.6","status":"unaffected"}]

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

The Events Calendar · GiveWPversion=n/a <4.16.6 changes=[{"at":"4.16.6","status":"unaffected"}]

Published CVSS scores

6.5PatchstackCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-862Missing Authorization

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo