dbcve.org
Follow My Blog PostWordPress extension · Wpwebelite

CVE-2025-64258

HIGH · 7.5 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to 2.4.0 or later.
See remediation →
84/100
Remediation priority · High
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 System Information to an Unauthorized Control Sphere vulnerability in wpweb Follow My Blog Post follow-my-blog-post allows Retrieve Embedded Sensitive Data.This issue affects Follow My Blog Post: from n/a through <= 2.3.9.

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 wpweb Follow My Blog Post WordPress plugin versions through 2.3.9 contains an information disclosure vulnerability that allows unauthorized actors to retrieve embedded sensitive data from the system. This exposure of sensitive system information occurs due to insufficient access controls on certain endpoints or functionality within the plugin.

MitigationUpdate the Follow My Blog Post plugin to the latest patched version immediately. Review server logs to determine if the vulnerability was exploited and consider rotating any credentials or sensitive data that may have been exposed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Follow My Blog PostWordPress extension
Affected:< 2.4.0

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Check the installed version of Follow My Blog Post plugin
    Navigate to WordPress admin > Plugins > Installed Plugins > Follow My Blog Post and view the version number displayed
    Affected if The version shown is earlier than 2.4.0 (for example 2.3.9, 2.3.8, etc.)
  2. Confirm the plugin is actively enabled on the site
    In WordPress admin > Plugins > Installed Plugins, verify the Follow My Blog Post plugin shows as 'Active'
    Affected if The plugin is active and the version is below 2.4.0
  3. Identify any publicly accessible endpoints related to the plugin
    Review the site's URL structure for any paths containing 'follow-my-blog-post', 'fmbp', or similar plugin-related keywords; also check wp-content/plugins/follow-my-blog-post for available PHP files
    Affected if Public endpoints exist that could be accessed without authentication
  4. Review server access logs for suspicious requests to plugin endpoints
    Examine web server access logs (Apache/nginx) for unusual GET or POST requests to plugin-related paths, particularly those that might retrieve data or configuration
    Affected if Logs show unauthorized external requests to plugin functionality since the plugin was installed
  5. Check for exposed sensitive data in plugin configuration
    Inspect the WordPress database or plugin settings page for any stored sensitive information such as API keys, tokens, or credentials that could be retrieved through the vulnerability
    Affected if Sensitive credentials or system information are stored in plugin settings accessible via the vulnerable endpoints

A site is affected if the Follow My Blog Post plugin version is below 2.4.0 and the plugin is active on a publicly accessible WordPress installation.

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.

dbcve · scoped
Upgrade available Upgrade to 2.4.0 or later
Fixed in 2.4.0
Interim mitigation

Update the Follow My Blog Post plugin to the latest patched version immediately. Review server logs to determine if the vulnerability was exploited and consider rotating any credentials or sensitive data that may have been exposed.

Recommended fix Moderate confidence

2.4.0

  1. 1. Create a full backup of the WordPress site (database and files) before updating.
  2. 2. Navigate to the WordPress admin dashboard > Plugins section.
  3. 3. Locate the Follow My Blog Post plugin in the installed plugins list.
  4. 4. If an update is available, click 'Update Now' to update to version 2.4.0, or manually upload and replace the plugin files with version 2.4.0.
  5. 5. After updating, verify the plugin is running version 2.4.0 by checking the Plugins page.
  6. 6. Test the plugin functionality to ensure the update did not break expected features.
  7. 7. Clear any caching mechanisms if the site uses caching.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Follow My Blog Post Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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