CVE-2026-107616 · Package
NO FIX YET · SEE WHAT TO DO
The Amelia booking plugin for WordPress up to and including 9.9.1 lets any logged-in customer request a CSV of attendee personal data for any event by changing the event ID. The exported data includes names, emails, phone numbers, dates of birth, private notes, payment details and uploaded-file URLs.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the Amelia plugin at version 9.9.1 or earlier where anyone with a logged-in customer account (the wpamelia-customer role) can reach the report endpoint. Sites that do not allow customer registration or logins, or that run a newer plugin version, are not exposed.
Not affected if no-customer-accounts, plugin-updated
Who cares amelia, self-hosted, wordpress
Version header of wp-content/plugins/ameliabooking/ameliabooking.phpwpamelia-customer role is what gives access9.9.1; the sources do not name the fixed versionThe Amelia plugin for WordPress is vulnerable to unauthorized access of attendee data due to a missing authorization check on the GetEventAttendeesCommandHandler::handle() function in versions up to, and including, 9.9.1. The handler only enforces the broad amelia_read_events capability — which the plugin's own wpamelia-customer role possesses — and does not verify that the authenticated user is an organizer/provider of the event referenced by the client-supplied id query parameter. This makes it possible for authenticated attackers, with wpamelia-customer-level access and above, to export the full CSV of attendee personally identifiable information (first/last name, email, phone, date of birth, gender, private notes, payment amounts/methods, WooCommerce order IDs, custom-field values, and uploaded-file URLs) for any Amelia event on the site by directly invoking the /report/event/attendees endpoint with an arbitrary event ID.
This page as .md ·
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.