CVE-2025-30890
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 SuitePlugins Login Widget for Ultimate Member login-widget-for-ultimate-member allows PHP Local File Inclusion.This issue affects Login Widget for Ultimate Member: from n/a through <= 1.1.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 confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the Login Widget for Ultimate Member WordPress plugin. The flaw allows attackers to manipulate filename parameters in include/require statements to read sensitive files from the server filesystem, potentially exposing configuration files, credentials, or other sensitive data.
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.
-
Check the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Login Widget for Ultimate Member. The version number is displayed under the plugin name. Alternatively, check the plugin's main PHP file or readme.txt for the 'Version' header.Affected if The installed version falls within the vulnerable version range (when known from official sources).
-
Confirm the plugin is activeIn WordPress admin, verify that Login Widget for Ultimate Member is activated. Check the plugins list where active plugins are marked as 'Active'.Affected if The plugin is active and the vulnerable code is reachable.
-
Identify vulnerable code pathsExamine plugin PHP files for include/require statements that use variable or user-controlled input for filename parameters. Look for patterns like 'include($filename)' or 'require($_GET[...])' without proper sanitization.Affected if The plugin contains include/require statements that accept unsanitized filename parameters accessible via HTTP requests.
-
Test for directory traversal capabilityIf accessible parameters are found, test them with a safe path like '/etc/passwd' or '../../wp-config.php' via a GET or POST request to the affected endpoint.Affected if The application returns the contents of the requested file, confirming LFI is exploitable.
A user is affected if they have a vulnerable version of the Login Widget for Ultimate Member plugin installed and active, with accessible include/require statements that allow directory traversal via filename parameters.
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 the Login Widget for Ultimate Member plugin to the latest patched version. If no patch is available, disable the plugin immediately and implement a Web Application Firewall rule as a temporary measure to block directory traversal patterns.
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30890 — 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-30890 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