dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2025-58269

MEDIUM · 5.3 CVSS v3.1 Published 2025-09-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
Use of Hard-coded Credentials vulnerability in weDevs WP Project Manager wedevs-project-manager allows Retrieve Embedded Sensitive Data.This issue affects WP Project Manager: from n/a through <= 2.6.25.

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

The WP Project Manager plugin by weDevs contains hardcoded credentials embedded in the codebase. This vulnerability allows an attacker to retrieve these embedded sensitive credentials, potentially leading to unauthorized access or data exposure. The issue affects versions up to and including 2.6.25.

MitigationReplace all hardcoded credentials with secure credential management methods such as environment variables or a secure configuration vault, and rotate any exposed credentials immediately.

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
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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. Verify WP Project Manager plugin is installed
    Check your WordPress site's wp-content/plugins directory or access the Plugins admin page to confirm the WP Project Manager plugin by weDevs is present
    Affected if The plugin is installed and active on the WordPress site
  2. Check installed plugin version
    Access the Plugins admin page in WordPress and locate the WP Project Manager plugin to view its installed version number, or inspect the plugin header in its main PHP file for the Version field
    Affected if The installed version is 2.6.25 or lower (any version up to and including 2.6.25)
  3. Search plugin source for hardcoded credentials
    Inspect the plugin source code files in the wp-project-manager directory for embedded strings that resemble credentials such as passwords, API keys, tokens, or secret keys. Look for suspicious static string assignments in PHP files
    Affected if Hardcoded credentials (passwords, API keys, tokens, or similar secrets) are found embedded in the plugin source code

A user is affected if the WP Project Manager plugin is installed with version 2.6.25 or lower and contains hardcoded credentials in its source files

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

Replace all hardcoded credentials with secure credential management methods such as environment variables or a secure configuration vault, and rotate any exposed credentials immediately.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58269 — 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-58269 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