CVE-2025-3300
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 · uneditedThe WPMasterToolKit (WPMTK) – All in one plugin plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 2.5.2. This makes it possible for authenticated attackers, with Administrator-level access and above, to read and modify the contents of arbitrary files on the server, which can contain sensitive information.
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 confidenceThe WPMasterToolKit WordPress plugin up to version 2.5.2 contains a directory traversal vulnerability that allows authenticated administrators to read and modify arbitrary files on the server by manipulating file paths, likely through insufficient validation of path traversal sequences (../) in file operation parameters.
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
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 WPMasterToolKit plugin is installedLocate the plugin in your WordPress installation at wp-content/plugins/ or check via WordPress admin dashboard under Plugins > Installed Plugins. Look for 'WPMasterToolKit' in the list.Affected if WPMasterToolKit appears in the installed plugins list
-
Check installed plugin versionOpen the main plugin file (typically wpmastertoolkit.php) in the plugin directory and locate the 'Version' header comment, or view the version displayed in the WordPress admin plugin list.Affected if Version number is 2.5.2 or lower (any version up to and including 2.5.2)
-
Confirm administrator access to the pluginLog into WordPress as an administrator and navigate to the WPMasterToolKit settings or tools section. Verify that admin-level users can access file-related operations.Affected if Administrator accounts can access the plugin's file operation features
-
Identify if file operation features accept path parametersWithin the WPMasterToolKit admin interface, locate any features that involve file reading, writing, importing, or exporting. Check if these features allow users to specify file paths as input parameters.Affected if The plugin provides file operation features (such as file import, export, or viewer) that accept file path inputs from users
Your environment is affected if WPMasterToolKit plugin is installed with version 2.5.2 or lower AND administrator users can access file operation features that accept path parameters, as the directory traversal vulnerability exists in those file operations.
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 plugin to a version beyond 2.5.2 once available. Until then, restrict administrator access to trusted users only, and consider disabling the affected file operation features if possible.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3300 — 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-3300 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