WpEvently

WpEvently: The CVSS vector permits an unauthenticated attacker. An operation lacks the required authorization checks. The vector indicates limited unauthorized information access and changes, with no availability impact scored. The export does not identify the protected resource, exact action or capability that is missing; more specific read or write operations are not established. The authoritative export does not name the vulnerable endpoint, request action, parameter or implementation function. Published affected versions: <= 5.7.8.

Event Booking Manager for WooCommerce from 5.3.6 up to but not including 5.6.0, a Contributor or higher can read stored PayPal and Stripe configuration, including secret keys, because access is not restricted to an authorized payment-settings manager. The export does not name the endpoint, action or configuration-reading function. Disclosure of these secrets can enable abuse of the associated gateway permissions; the export does not establish any specific transaction performed by an attacker.

Event Booking Manager for WooCommerce from 5.3.6 up to but not including 5.3.8, an unauthenticated caller can supply an enumerable booking reference to a confirmation view that lacks ownership or authorization checks. It returns attendee full names, email addresses, phone numbers and custom registration fields. Only sites using the plugin's native non-WooCommerce checkout are affected; that checkout is not the default. The export does not name the confirmation route or reference parameter.

WpEvently through 5.6.0 has an insecure direct object reference: an unauthenticated caller can select an object without the required authorization check. The CNA rates the resulting impact as unauthorized modification and reduced availability, with no confidentiality impact. Version 5.6.4 is identified as unaffected.

WpEvently through 5.5.0 does not enforce the authorization required for an affected operation. A Subscriber can cross that boundary and read protected event or plugin information.

WpEvently through 5.5.0 does not enforce the authorization required for an affected operation. A Contributor can cross that boundary and change protected event or plugin state, with limited availability impact.

Event Booking Manager for WooCommerce through 5.3.7 registers the authenticated AJAX action mep_save_payment_settings_modal without nonce verification. The ajax_save_payment_settings_modal() handler authorizes anyone with either manage_options or edit_posts, so a Contributor satisfies the check. It reads attacker-controlled POST values including mep_enable_wc_payment, mep_wc_add_to_cart_redirect, mep_wc_after_order_redirect, mep_wc_require_login, mep_confirmation_page_id, and mep_wc_confirm_ticket_status, then writes them to the site-wide payment_setting_sec option. A Contributor can therefore change payment enablement, checkout redirects, login requirements, confirmation-page selection, and which order statuses confirm tickets for every event booking. Version 5.3.8 verifies the mep_save_payment_settings nonce and requires manage_options.

WpEvently is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is n/a through 5.3.3.

WpEvently is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request. The published affected range is n/a through 4.1.2.

WpEvently is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is <= 5.1.4.

WpEvently is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

WpEvently is affected by code execution. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can run attacker-controlled code in the WordPress hosting account.

WpEvently is affected by code execution. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can run attacker-controlled code in the WordPress hosting account.

WpEvently is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.

WpEvently is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

WpEvently is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

WpEvently is affected by code execution. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can run attacker-controlled code in the WordPress hosting account.

WpEvently is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

WpEvently is affected by cross-site scripting. Exploitation requires an authenticated contributor account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

WpEvently is affected by code execution. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can run attacker-controlled code in the WordPress hosting account.

WpEvently is affected by filesystem traversal. Exposure depends on how the affected operation is made reachable by the site. A crafted path can escape the intended directory and reach files or directories elsewhere on the server.

WpEvently is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

WpEvently is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

Event Manager for WooCommerce is affected by filesystem traversal. Exposure depends on how the affected operation is made reachable by the site. A crafted path can escape the intended directory and reach files or directories elsewhere on the server.

Event Manager and Tickets Selling Plugin for WooCommerce – WpEvently – WordPress Plugin is affected by code execution. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can run attacker-controlled code in the WordPress hosting account.

Mage Eventpress is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

Mage Eventpress is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.

Mage Eventpress is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.