CVE-2025-47510
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in fullworks Display Eventbrite Events widget-for-eventbrite-api allows PHP Local File Inclusion.This issue affects Display Eventbrite Events: from n/a through < 6.3.
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 confidenceA PHP Local File Inclusion vulnerability in the fullworks Display Eventbrite Events WordPress plugin allows attackers to include and execute arbitrary local PHP files by manipulating include/require statements, potentially leading to remote code execution. The vulnerability exists in versions prior to 6.3.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the plugin filesCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'display-eventbrite-events' or similar. Also check wp-content/plugins/display-eventbrite-events/ for the main plugin file (usually display-eventbrite-events.php or similar).Affected if The plugin folder exists in the WordPress installation
-
Read the plugin versionOpen the main plugin PHP file and look for a version comment, version constant, or the plugin header which typically contains 'Version: x.x.x'Affected if The version number found is less than 6.3 or no version is specified (indicating an older release)
-
Check WordPress admin panelIn the WordPress admin, go to Plugins > Installed Plugins and look for 'Display Eventbrite Events' in the list. The version will be displayed under the plugin name.Affected if The plugin shows as installed with a version listed below 6.3
-
Verify the plugin is activeIn WordPress admin under Plugins > Installed Plugins, confirm whether the Display Eventbrite Events plugin is activated. The vulnerability requires the plugin to be active to be exploitable.Affected if The plugin is active and the version is below 6.3
You are affected if the Display Eventbrite Events plugin is installed and active with a version number lower than 6.3.
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 the Display Eventbrite Events plugin to version 6.3 or later to patch the file inclusion vulnerability. If immediate update is not possible, disable the plugin until the patch can be applied.
6.3
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the 'Display Eventbrite Events' plugin
- Check if the current version is below 6.3
- If below 6.3, click 'Update Now' to upgrade to version 6.3 or later
- Verify the update was successful and test that the plugin functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47510 — 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-2025-47510 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