CVE-2025-32629
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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in CMSJunkie - WordPress Business Directory Plugins WP-BusinessDirectory wp-businessdirectory allows Path Traversal.This issue affects WP-BusinessDirectory: from n/a through <= 3.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 · moderate confidenceA path traversal vulnerability exists in the WP-BusinessDirectory WordPress plugin (versions up to 3.1.2) that allows attackers to access files outside the web root directory through manipulation of file path inputs using '..' sequences. This improper input validation could enable unauthorized file system access.
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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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-BusinessDirectory plugin is installedLog in to WordPress admin panel and navigate to Plugins > Installed Plugins. Look for WP-BusinessDirectory in the list of active plugins.Affected if The plugin appears in the installed plugins list, regardless of activation status, the environment could be affected.
-
Determine the installed plugin versionIn the WordPress admin under Plugins > Installed Plugins, find WP-BusinessDirectory and note the version number displayed beneath the plugin name. Alternatively, inspect the plugin header in wp-content/plugins/business-directory-plugin/main.php or similar main plugin file.Affected if The installed version is 3.1.2 or any earlier version, making the installation vulnerable to path traversal.
-
Check if file handling features are activeNavigate to the plugin settings in WordPress admin panel under Business Directory > Settings or similar. Look for file upload, attachment, import, or file download functionalities that accept user-supplied file paths.Affected if File-related features such as attachments, uploads, or file listing are enabled, the path traversal vulnerability can be exploited through these interfaces.
-
Review access logs for path traversal attemptsExamine web server access logs (Apache error.log, Nginx access.log, or WordPress debug.log) for requests containing '..' sequences in parameters related to the plugin, such as '?file=../' or URL-encoded '..' patterns targeting plugin endpoints.Affected if Any recent or historical requests with '..' sequences directed at plugin URLs indicate potential exploitation attempts.
If the WP-BusinessDirectory plugin version is 3.1.2 or lower and file handling features are in use, the environment is affected by this path traversal vulnerability.
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, implement strict input validation and path sanitization to restrict file access to allowed directories, and consider temporarily disabling the plugin until a fix is applied.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32629 — 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-32629 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