dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-49284

MEDIUM · 5.3 CVSS v3.1 Published 2024-10-17
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
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in BogdanFix WP SendFox wp-sendfox allows Retrieve Embedded Sensitive Data.This issue affects WP SendFox: from n/a through <= 1.3.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 · moderate confidence

The WP SendFox WordPress plugin versions up to 1.3.1 contain a vulnerability allowing unauthorized actors to retrieve embedded sensitive data, likely API keys or authentication tokens stored in the plugin configuration. The plugin fails to properly restrict access to this sensitive information, enabling authenticated or unauthenticated users to obtain credential data.

MitigationUpgrade WP SendFox to the latest version. If no patch is available, audit and rotate any API keys or credentials stored in the plugin, and consider disabling the plugin until a fix is released.

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 SendFox plugin version
    Log into WordPress admin, go to Plugins > Installed Plugins, locate SendFox (or SendFox - WP Mail Catcher), and read the version number from the plugin description. Alternatively, inspect /wp-content/plugins/sendfox/includes/ or the main plugin file for the 'Version' header comment.
    Affected if The installed version is 1.3.1 or lower.
  2. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that the SendFox plugin shows as 'Active'. An inactive plugin may not expose the vulnerability.
    Affected if The plugin is active and the version is 1.3.1 or lower.
  3. Check for stored API credentials
    Access the plugin settings page under Settings > SendFox (or similar). Look for fields labeled API Key, API Token, Access Token, or Auth Token. These fields should be masked or hidden (showing dots or asterisks). If full credentials are visible in plaintext, the flaw is present.
    Affected if Sensitive credential fields display plaintext values or are not properly obscured.
  4. Test unauthenticated access to settings
    Log out of WordPress and attempt to access the SendFox plugin settings page directly via its URL (commonly /wp-admin/options-general.php?page=sendfox or similar). If the page loads without requiring authentication, the access control flaw is present.
    Affected if Unauthenticated access is granted to plugin settings or credential data.
  5. Inspect plugin source for exposed endpoints
    If you have file access, examine the main plugin PHP files in /wp-content/plugins/sendfox/ for any AJAX actions, REST API routes, or direct file includes that lack capability checks (like 'manage_options' or 'edit_posts'). Look for functions that return API keys or settings without verification.
    Affected if Code reveals unauthenticated endpoints that return sensitive configuration data.

A user is affected if the WP SendFox plugin version is 1.3.1 or lower AND the plugin is active AND sensitive credentials are visible to unauthorized users or accessible without authentication.

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 WP SendFox to the latest version. If no patch is available, audit and rotate any API keys or credentials stored in the plugin, and consider disabling the plugin until a fix is released.

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

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

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