dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2025-58659

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 Essekia Helpie FAQ helpie-faq allows Retrieve Embedded Sensitive Data.This issue affects Helpie FAQ: from n/a through <= 1.45.

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 confidence

Use of hard-coded credentials in the Helpie FAQ WordPress plugin (versions up to 1.45) allows unauthenticated attackers to retrieve embedded sensitive data. The credentials are hardcoded directly in the plugin's source code, making them discoverable through code review or decompilation.

MitigationReplace all hardcoded credentials with proper credential management mechanisms such as WordPress options with encryption, environment variables, or a secrets management solution, 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 Helpie FAQ plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Helpie FAQ' or check the /wp-content/plugins/ directory for a folder named 'helpie-faq'
    Affected if The plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, click on the Helpie FAQ plugin to view its details and compare the version number to 1.45 or lower; alternatively, read the main plugin file header for the Version field
    Affected if The installed version is 1.45 or lower
  3. Inspect plugin source for hardcoded credentials
    Examine PHP files in the helpie-faq plugin directory, looking for variables or strings that appear to be credentials (such as API keys, tokens, passwords, or secrets) defined directly in the code rather than loaded from configuration
    Affected if Hardcoded credential strings are found in any plugin PHP file
  4. Check for sensitive data exposure
    Search plugin source code for patterns like 'password', 'secret', 'key', 'token', 'auth', 'api_key' used as literal string values (not function parameters) that could be used for authentication or data retrieval
    Affected if Credentials are embedded as static string values in the code

If the Helpie FAQ plugin is installed at version 1.45 or lower and its source code contains hardcoded credentials, the environment is affected by this CVE.

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 proper credential management mechanisms such as WordPress options with encryption, environment variables, or a secrets management solution, 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-58659 — 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-58659 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