Event Manager And Tickets Selling Plugin For WoocommerceWordPress extension · Mage People
CVE-2022-47164
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in MagePeople Team Event Manager and Tickets Selling Plugin for WooCommerce plugin <= 3.7.7 versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the MagePeople Team Event Manager and Tickets Selling Plugin for WooCommerce. The plugin fails to properly validate anti-CSRF tokens (nonces) on sensitive actions, allowing authenticated attackers to trick site administrators or users into performing unintended operations such as modifying event settings, creating/deleting tickets, or altering purchase configurations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Event Manager And Tickets Selling Plugin For WoocommerceWordPress extension
<= 3.7.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installationCheck if 'Mage People Event Manager And Tickets Selling Plugin For Woocommerce' is installed in WordPress via wp-admin/plugins.php or by searching for the plugin folder in /wp-content/plugins/Affected if Plugin is present on the WordPress site
-
Identify installed versionLook up the plugin version in the plugin header (plugin main file) or in WordPress admin plugin list under the 'Version' columnAffected if Version number is 3.7.7 or lower
-
Verify vulnerable functionality existsCheck if the plugin admin panel (wp-admin/admin.php?page=mage-event-manager) or frontend event/ticket AJAX endpoints are accessible and activeAffected if Plugin functionality for event settings, ticket management, or purchase configurations is enabled and accessible
-
Confirm nonce validation is missingReview plugin PHP files for missing wp_verify_nonce, check_admin_referer, or wp_nonce_field calls on state-changing actions (event creation, ticket deletion, settings updates)Affected if Sensitive admin or AJAX actions lack proper nonce verification code
If the plugin is installed with version 3.7.7 or lower and has active event/ticket management functionality, the site is vulnerable to CSRF attacks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement anti-CSRF token validation (nonce checks) on all state-changing plugin actions, including admin panel operations and frontend AJAX endpoints. Users should update to version 3.7.8 or later when available.
Fix this in Event Manager And Tickets Selling Plugin For Woocommerce
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47164 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-47164 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data