mediumCVE-2026-11354

Participants Database <= 2.7.8.3 - Missing Authorization to Unauthenticated Arbitrary Record Update / Sensitive Information Exposure via 'id' Parameter

Q: What is affected by CVE-2026-11354?

xnau Participants Database versions listed as affected should be reviewed: <= 2.7.8.3, up to and including 2.7.8.3.

Q: What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

Q: How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

Q: How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.

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.

Browse WordPress security risks

ProductParticipants Database

CVSS5.3

EPSSNot scored yet

UpdatedJuly 24, 2026

Quick answer

xnau Participants Database should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

<= 2.7.8.3
up to and including 2.7.8.3

Fixed versions

2.7.8.4

How to fix it

CVE-2026-11354 affects Participants Database and involves authorization failure. Successful exploitation may let a lower-privileged user view or change data outside their allowed scope. Treat this as a high-priority fix, especially when the affected component or endpoint is reachable by untrusted users. Upgrade Participants Database to 2.7.8.4 or a later vendor-supported fixed release.

Inventory every deployment, device, package, plugin, container, build, and environment that uses Participants Database.
Compare the installed version with the recorded affected range: <= 2.7.8.3, *-2.7.8.3.
Upgrade Participants Database to 2.7.8.4 or a later vendor-supported fixed release.
Until patched, disable the affected Participants Database feature or plugin and restrict its public and administrator endpoints.
Review configuration, roles, tokens, network paths, and exposed endpoints connected to Participants Database; remove access that is not required.
Review authentication, API, audit, and object-change logs for cross-user access, bypassed checks, or unexpected privileged actions.
If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-11354 in place.
Use a safe regression test to confirm the affected authorization failure path no longer produces the vulnerable behavior.
Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.

Related categories

WordPress Authorization Bypass Information Disclosure

Related security risks

More published guidance from the same primary category.

high

CVE-2026-65500 Manual - Documentation, Knowledge Base & Education WordPress Theme vulnerability

Updated July 24, 2026

medium

Kirki <= 6.0.14 - Insecure Direct Object Reference to Unauthenticated Sensitive Information Disclosure via 'context' Parameter

Updated July 24, 2026

medium

Payment Plugins for Stripe WooCommerce <= 4.0.7 - Missing Authorization to Unauthenticated Arbitrary Order Status Modification via Empty Webhook Secret

Updated July 24, 2026

Trusted references

Source advisoryNVD, Wordfence Source advisoryNVD, Wordfence Source advisoryNVD, Wordfence Source advisoryNVD, Wordfence Source advisoryNVD, Wordfence Source advisoryNVD, Wordfence Wordfence advisoryNVD, Wordfence Wordfence advisoryNVD, Wordfence

FAQ

What is affected by CVE-2026-11354?

xnau Participants Database versions listed as affected should be reviewed: <= 2.7.8.3, up to and including 2.7.8.3.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.