dbcve.org
Xt Event Widget For Social EventsWordPress extension · Xylusthemes

CVE-2025-47531

HIGH · 8.8 CVSS v3.1 Published 2025-05-07
Fix available
A fix is available. Upgrade to 1.1.8 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Xylus Themes XT Event Widget for Social Events xt-facebook-events allows PHP Local File Inclusion.This issue affects XT Event Widget for Social Events: from n/a through <= 1.1.7.

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

Local File Inclusion vulnerability in Xylus Themes XT Event Widget for Social Events allows attackers to manipulate file paths in PHP include/require statements to load arbitrary local files, potentially achieving remote code execution. The vulnerability exists in the xt-facebook-events component through version 1.1.7 due to improper validation of user-supplied file path parameters.

MitigationUpdate to a patched version of the XT Event Widget plugin; if unavailable, disable the plugin. Implement strict input validation on file path parameters and deploy WAF rules to block directory traversal patterns (../, etc.) as an interim measure.

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
Xt Event Widget For Social EventsWordPress extension
Affected:< 1.1.8

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

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

  1. Locate the XT Event Widget plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'xt-facebook-events', 'xt-event-widget', or similar Xylusthemes plugin directories. Use file system inspection or a WordPress admin panel plugin list.
    Affected if The plugin folder is present in the plugins directory
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually named plugin-name.php) in the plugin folder and look for a version comment or header that specifies 'Version: x.x.x'. Alternatively, check the WordPress plugin admin page which displays installed versions.
    Affected if The version shown is 1.1.7 or lower (any version below 1.1.8)
  3. Verify vulnerable include/require code exists
    Search within the plugin folder for PHP include, include_once, require, or require_once statements that use variables or parameters without sanitization. Look for patterns like 'include($var)', 'require($_GET[...])', or similar unsanitized file path constructions.
    Affected if Unsanitized include/require statements using request parameters or variables are found in the plugin code
  4. Check web server protections
    Inspect the PHP configuration (php.ini) for the allow_url_include setting and verify web root file permissions are restrictive (files should not be world-writable). Check .htaccess or server configuration for additional access controls.
    Affected if allow_url_include is enabled or web root has overly permissive access rights

A user is affected if the XT Event Widget for Social Events plugin version is below 1.1.8 and the vulnerable include/require code pattern is present in their installation.

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

Update to a patched version of the XT Event Widget plugin; if unavailable, disable the plugin. Implement strict input validation on file path parameters and deploy WAF rules to block directory traversal patterns (../, etc.) as an interim measure.

Recommended fix High confidence

Version 1.1.8

  1. Update the XT Event Widget for Social Events plugin to version 1.1.8 or later
  2. After updating, verify the plugin version reflects 1.1.8 or higher in the WordPress admin plugin list
  3. Review plugin settings and functionality to ensure the update did not introduce unintended changes
  4. If available, review the plugin's changelog for any security-related notes or additional configuration requirements

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

Fix this in Xt Event Widget For Social Events Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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