dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-48158

HIGH · 8.6 CVSS v3.1 Published 2025-08-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Alex Githatu BuddyPress XProfile Custom Image Field buddypress-xprofile-image-field allows Path Traversal.This issue affects BuddyPress XProfile Custom Image Field: from n/a through <= 3.0.1.

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 confidence

A path traversal vulnerability in the BuddyPress XProfile Custom Image Field plugin (versions <=3.0.1) allows attackers to use '..' sequences in file path inputs to access files outside the intended directory, potentially reading sensitive files or bypassing access controls.

MitigationUpgrade to the latest version of BuddyPress XProfile Custom Image Field. If no patch is available, disable the plugin until a fix is released. Implement input validation to sanitize file path references and restrict file access to intended directories.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the plugin is installed
    Check the WordPress plugins directory for the 'buddypress-xprofile-custom-image-field' folder at wp-content/plugins/
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Verify the installed version
    Access WordPress admin > Plugins and look at the version number listed for 'BuddyPress XProfile Custom Image Field', or read the main plugin file header
    Affected if The installed version is 3.0.1 or any version lower than 3.0.1
  3. Confirm the plugin is active
    Check WordPress admin > Plugins to see if the plugin is currently activated
    Affected if The plugin is active and the version is 3.0.1 or below
  4. Check if XProfile image fields are in use
    Navigate to BuddyPress > Profile Fields in the WordPress admin and look for any custom image field types created using this plugin
    Affected if The plugin is active and profile image fields are configured, exposing the traversal vulnerability

You are affected if the BuddyPress XProfile Custom Image Field plugin is installed, active, and running version 3.0.1 or below with active profile image fields configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to the latest version of BuddyPress XProfile Custom Image Field. If no patch is available, disable the plugin until a fix is released. Implement input validation to sanitize file path references and restrict file access to intended directories.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-48158 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-48158 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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