CVE-2025-30868
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 Maidul Team Manager wp-team-manager allows PHP Local File Inclusion.This issue affects Team Manager: from n/a through <= 2.1.23.
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 · moderate confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the wp-team-manager WordPress plugin. The vulnerability stems from improper control of filenames in include/require statements, allowing attackers to include arbitrary PHP files from the server, potentially leading 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
- 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.
-
Verify wp-team-manager plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'wp-team-manager', or check the /wp-content/plugins/ directory for the wp-team-manager folderAffected if The plugin is installed and active on the WordPress site
-
Identify the installed version of wp-team-managerCheck the plugin's main PHP file header for the Version comment, or look at the plugin details in WordPress admin plugins listAffected if The version is unknown, unpatched, or falls within any known vulnerable range
-
Locate file inclusion code in the pluginSearch plugin PHP files for include, require, include_once, or require_once statements that use variables or parameters without sanitization (e.g., include($_GET['file']) or include($path))Affected if The plugin contains dynamic file inclusion using unsanitized input
-
Test for accessible LFI parametersIdentify URL parameters used in file inclusion functions, then attempt to include a known safe file (e.g., ../../../wp-config.php) to verify if the vulnerability is exploitableAffected if The file inclusion accepts path traversal sequences and returns file contents
-
Check PHP configuration settingsReview php.ini or phpinfo() for allow_url_include setting; also check for open_basedir restrictionsAffected if allow_url_include is enabled (though this affects RFI more than LFI)
You are affected if wp-team-manager plugin is installed and contains exploitable dynamic file inclusion code that accepts user-controlled path parameters without proper sanitization.
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 wp-team-manager to the latest patched version. If no patch is available, disable the plugin. Additionally, disable allow_url_include in PHP configuration and implement strict input validation on all file inclusion parameters.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30868 — 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-30868 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