dbcve.org
Simple Event PlannerWordPress extension · Presstigers

CVE-2022-25611

MEDIUM · 5.4 CVSS v3.1 Published 2022-03-25
Fix available
A fix is available. Upgrade to after 1.5.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Authenticated Stored Cross-Site Scripting (XSS) in Simple Event Planner plugin <= 1.5.4 allows attackers with contributor or higher user roles to inject the malicious script by using vulnerable parameter &custom[add_seg][].

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 confidence

Authenticated stored XSS vulnerability in Simple Event Planner plugin versions 1.5.4 and below allows contributors to inject malicious JavaScript via the custom[add_seg][] parameter. The injected payload persists and executes when other users view the affected content.

MitigationApply input sanitization (sanitize_text_field, wp_kses) to the custom[add_seg][] parameter and implement proper output encoding when displaying user-supplied data. Update to patched version if available.

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
Affected:<= 1.5.4

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Simple Event Planner installation
    Check your WordPress plugins directory or wp-content/plugins/simple-event-planner folder for the plugin. Read the main PHP file (e.g., simple-event-planner.php) to find the declared version number.
    Affected if The installed version is 1.5.4 or lower as stated in the plugin headers.
  2. Verify contributor user role exists
    In WordPress admin, navigate to Users > All Users and check if any users have the Contributor role assigned.
    Affected if Contributor users exist and have access to create or edit event content through the plugin.
  3. Inspect stored custom[add_seg] data in database
    Query the WordPress database (wp_postmeta table) for meta_key containing 'add_seg' or review the plugin's event creation form submission. Look for unescaped HTML or script tags in meta_value fields related to segment data.
    Affected if The custom[add_seg][] parameter values are stored without sanitization (sanitize_text_field or wp_kses not applied).
  4. Check event display pages for unencoded output
    Visit frontend pages where events are displayed (event listings, single event pages). View page source and search for content from the custom[add_seg][] field. Verify if <script> tags, event handlers (onclick, onerror), or HTML tags render as plain text or execute.
    Affected if User-supplied data from custom[add_seg][] renders as raw HTML or executes JavaScript when other users view the event.

You are affected if the Simple Event Planner plugin version is 1.5.4 or lower and contributor-role users can create events with unsanitized content in the custom[add_seg][] parameter that renders unencoded in the browser.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.5.4
Interim mitigation

Apply input sanitization (sanitize_text_field, wp_kses) to the custom[add_seg][] parameter and implement proper output encoding when displaying user-supplied data. Update to patched version if available.

Recommended fix Moderate confidence

Simple Event Planner version 1.5.5 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Simple Event Planner in the plugin list
  4. Check if an update is available and update to the latest version (version 1.5.5 or higher)
  5. Alternatively, navigate to Dashboard > Updates and update all plugins
  6. Verify the update was successful by checking the plugin version

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
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25611 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-25611 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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