CVE-2025-47672
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 miniOrange miniOrange Discord Integration miniorange-discord-integration allows PHP Local File Inclusion.This issue affects miniOrange Discord Integration: from n/a through <= 2.2.2.
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 miniOrange Discord Integration WordPress plugin versions up to 2.2.2 allows attackers to include and potentially execute arbitrary local PHP files via insecure include/require statements, which could lead to remote code execution.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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.
-
Verify plugin installation and versionAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'miniOrange Discord Integration' and check the version number displayed under the plugin name. Alternatively, inspect the main plugin file (usually mo-oauth-discord.php) or readme.txt in wp-content/plugins/mo-oauth-discord/ for the Version header.Affected if The plugin version is 2.2.2 or lower, or if no version is displayed (implying an unpatched older version).
-
Confirm plugin is activeIn the WordPress admin under Plugins > Installed Plugins, verify that the miniOrange Discord Integration plugin shows as 'Active' (not just installed).Affected if The plugin is active and the version is 2.2.2 or lower.
-
Identify vulnerable file inclusion parameterInspect the plugin source code for include/require statements that use variables without proper sanitization, typically patterns like 'include($_GET["page"])' or 'require($file)'. Check PHP files in the plugin directory for dynamic file inclusion using request parameters.Affected if The plugin contains insecure include/require statements that use user-supplied input (GET/POST parameters) without validation, and the version is 2.2.2 or lower.
-
Check PHP configuration for allow_url_includeCreate a PHP info page or check php.ini directly for the allow_url_include setting. Look for 'allow_url_include = On' in the configuration.Affected if allow_url_include is enabled (On), which combined with the LFI vulnerability could allow remote file inclusion escalation.
You are affected if the miniOrange Discord Integration plugin is active at version 2.2.2 or lower and contains the insecure file inclusion code pattern described in the CVE.
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.
From vendor dataUpdate to a patched version of the plugin if available; otherwise, disable the plugin immediately and implement input validation on file inclusion parameters or disable allow_url_include in PHP configuration.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47672 — 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-47672 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