CVE-2026-11354: Participants Database <= 2.7.8.3 - Missing Authorization to Unauthenticated Arbitrary Record Update / Sensitive Information Exposure via 'id' Parameter
The Participants Database plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.7.8.3 via the 'id' parameter. This makes it possible for unauthenticated attackers to overwrite arbitrary participant records by numeric ID and redirect the private_id-bearing record-access link to an attacker-controlled email address, granting full read and edit access to the victim's stored personally identifiable information including names, email addresses, phone numbers, and any other fields collected in the participant database. An attacker can harvest a valid nonce with a plain unauthenticated GET request to any page rendering the public signup or record form, then POST action=update with an arbitrary id value to overwrite any record; chaining a subsequent action=retrieve then delivers the private-access link to the attacker-controlled mailbox.
Security readout for executives and security teams
Plain-English summary
A flaw in the Participants Database WordPress plugin can let an unauthenticated visitor alter participant records and redirect private record-access links to an email address they control. This may expose names, email addresses, phone numbers, and other collected personal information. The source bundle identifies versions through 2.7.8.3 as affected.
Executive priority
Prioritize prompt assessment where this plugin stores customer, member, employee, or applicant information. Restrict exposure and preserve logs while confirming vendor remediation. Escalate urgency for internet-facing forms or databases containing substantial personal information, even though the published severity is medium and active exploitation is not established.
Technical view
CVE-2026-11354 is a missing-authorization issue (CWE-862). Publicly rendered signup or record forms can expose request authorization material that does not prevent an anonymous user from targeting another numeric record ID. The attacker may change a record's email destination and obtain its private-access link. The supplied CVSS 3.1 score is 5.3.
Likely exposure
WordPress sites using Participants Database 2.7.8.3 or earlier are potentially exposed, particularly when public signup or record forms are reachable. Business impact depends on whether participant records contain personal or sensitive fields. The bundle's affected-version metadata is imperfect, so confirm installed versions directly.
Exploitation context
The described attack is remote, requires no account or user interaction, and has low stated complexity. However, the bundle marks this CVE as absent from KEV and provides no evidence of active exploitation. Treat exploitation as technically plausible, not confirmed in the wild.
Researcher notes
The stated CVSS vector records limited integrity impact and no confidentiality impact, while the narrative describes access to stored personal information. That inconsistency warrants cautious interpretation. The referenced source code and changeset support technical review, but the bundle does not explicitly identify a fixed release or provide evidence of real-world exploitation.
Mitigation direction
Inventory WordPress sites for Participants Database and identify versions at or below 2.7.8.3.
Check vendor or WordPress guidance for a corrected release; the source bundle does not name a fixed version.
Restrict public access to affected forms until corrected guidance is confirmed, where business requirements permit.
Review participant records and access-link emails for unauthorized changes or unexpected recipients.
Validation and detection
Confirm the installed plugin version from each WordPress instance, not only asset inventory records.
Identify publicly reachable pages rendering Participants Database signup or record forms.
Verify in an authorized staging environment that anonymous visitors cannot modify existing records.
Check whether private record links can be redirected to an untrusted email address.
Review record histories, application logs, and email records for unexplained recipient or profile changes.
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-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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
5Timeline events
0ADP providers
6Source 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-862 · source CWE mapping
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.