Simple Event PlannerWordPress extension · Presstigers
CVE-2022-25612
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 · uneditedMultiple Authenticated Persistent Cross-Site Scripting (XSS) vulnerabilities in Simple Event Planner WordPress plugin <= 1.5.4 allows user with author or higher user rights inject the malicious code via vulnerable parameters: &custom[event_organiser], &custom[organiser_email], &custom[organiser_contact].
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 · high confidenceAuthenticated persistent XSS in Simple Event Planner WordPress plugin <=1.5.4 allows author-level users to inject malicious JavaScript via the custom[event_organiser], custom[organiser_email], and custom[organiser_contact] parameters when creating or editing events. The injected scripts execute whenever event data is displayed to users.
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
Simple Event PlannerWordPress extension
<= 1.5.4CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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.
-
Verify Simple Event Planner plugin is installedNavigate to WordPress admin dashboard > Plugins and confirm Presstigers Simple Event Planner is listed as an active pluginAffected if Plugin is installed and active in WordPress
-
Check installed plugin versionIn the Plugins admin page, find Simple Event Planner and note the version number displayed beneath the plugin nameAffected if Version is 1.5.4 or lower (any version up to and including 1.5.4)
-
Inspect database for stored organizer fieldsQuery the WordPress postmeta table for meta_key values matching event_organiser, organiser_email, or organiser_contact; examine each value for unsanitized HTML tags such as script, iframe, or event handlers like onload/onerrorAffected if Any event post contains raw script tags, iframe elements, or JavaScript event handlers in these three organizer-related fields
You are affected if the Simple Event Planner plugin version is 1.5.4 or lower AND your site contains events with malicious scripts stored in the event_organiser, organiser_email, or organiser_contact fields.
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.
dbcve · scopedUpdate Simple Event Planner plugin to version >1.5.4 which includes proper input sanitization and output encoding for the affected event organizer fields; alternatively, implement server-side sanitization for these three parameters.
Simple Event Planner version 1.5.5 or latest available
- 1. Log in to the WordPress admin dashboard with an administrator account
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate 'Simple Event Planner' in the plugin list
- 4. If an update is available, click 'Update Now' to install the latest patched version
- 5. After updating, verify the plugin is running version 1.5.5 or higher under Plugins > Installed Plugins
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Simple Event Planner
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25612 — 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-25612 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