dbcve.org
EventinWordPress extension · Themewinter

CVE-2025-49321

MEDIUM · 6.1 CVSS v3.1 Published 2025-06-27
Fix available
A fix is available. Upgrade to 4.0.29 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Arraytics Eventin wp-event-solution allows Reflected XSS.This issue affects Eventin: from n/a through <= 4.0.28.

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

Reflected XSS vulnerability in the Eventin WordPress plugin (versions up to 4.0.28) allows attackers to inject malicious JavaScript via unsanitized user input that gets reflected in web pages without proper output encoding.

MitigationUpdate Eventin plugin to the latest version once available; apply vendor patch or manually sanitize all user inputs using WordPress escaping functions (esc_html(), esc_attr(), esc_url()) before output.

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
EventinWordPress extension
Affected:< 4.0.29

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate installed Eventin plugin version
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, find Eventin plugin, and read the version number displayed. Alternatively, check the plugin's main PHP file (typically at wp-content/plugins/eventin/eventin.php) for the 'Version' header comment.
    Affected if Version number is lower than 4.0.29 (for example, 4.0.28, 4.0.27, etc.)
  2. Confirm plugin is active on the site
    Verify that the Eventin plugin is installed AND activated. Check WordPress admin under Plugins > Installed Plugins for a status of 'Active'. Also verify that Eventin shortcodes or widgets are in use on any published pages.
    Affected if Plugin is both installed and active, with version below 4.0.29
  3. Identify exposed Eventin functionality
    Review site pages using Eventin features such as event calendars, event listings, registration forms, or event details pages. Note which Eventin shortcodes (e.g., [eventin_events], [event_details]) or templates are publicly accessible.
    Affected if Any Eventin-generated pages are publicly accessible on the site
  4. Inspect HTTP parameters for lack of encoding
    Manually test Eventin pages by appending common query parameters (such as ?event_id=, ?search=, or ?category=) with test alphanumeric values, then view the page source to verify if the values are properly escaped using esc_html(), esc_attr(), or similar functions.
    Affected if Input values appear unescaped/raw in the HTML output rather than as encoded entities

The environment is affected if the Eventin plugin version is below 4.0.29 and the plugin is active on the site, exposing users to reflected XSS through unsanitized user input.

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 4.0.29 or later
Fixed in 4.0.29
Interim mitigation

Update Eventin plugin to the latest version once available; apply vendor patch or manually sanitize all user inputs using WordPress escaping functions (esc_html(), esc_attr(), esc_url()) before output.

Recommended fix High confidence

Eventin version 4.0.29

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Eventin plugin (wp-event-solution)
  4. Check the current version to confirm it is 4.0.28 or earlier
  5. Click on 'Update now' if an update to version 4.0.29 or later is available
  6. Alternatively, navigate to Dashboard > Updates and select Eventin to update
  7. After updating, verify the plugin version shows 4.0.29 or higher
  8. Test the affected functionality to confirm the XSS vulnerability is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Eventin Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49321 — 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-2025-49321 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