CVE-2025-64258: Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in wpweb Follow My Bl

Q: How do I fix CVE-2025-64258?

follow my blog post: upgrade to 2.4.0. Exact commands for each OS are on this page.

Q: Is CVE-2025-64258 being exploited?

CVE-2025-64258 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-64258 affect?

CVE-2025-64258 affects follow my blog post. Severity is high (CVSS 7.5). 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.

Q: How urgent is CVE-2025-64258?

Priority 39/100. High severity; Remotely exploitable, no login, no user action

Routine

HIGH 7.5REMOTEUPGRADE

CVE-2025-64258 is a high-severity flaw (CVSS 7.5) affecting follow my blog post. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 70%)
CISA exploited list	No
Weakness	CWE-497
Published	2025-12-18
Last modified	2026-06-17

Publisher (CNA): Patchstack · Vendor: wpwebelite

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-12-18 08:16 UTCPublished CVE record published
2026-06-17 09:54 UTCUpdated Record last modified

wpwebelite follow my blog post UPGRADE

Affected: < 2.4.0

Fixed in: 2.4.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy follow-my-blog-post || rpm -q follow-my-blog-post || follow-my-blog-post --version

2. UPGRADE to 2.4.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade follow-my-blog-post

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade follow-my-blog-post

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-64258?

follow my blog post: upgrade to 2.4.0. Exact commands for each OS are on this page.

Is CVE-2025-64258 being exploited?

CVE-2025-64258 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-64258 affect?

CVE-2025-64258 affects follow my blog post. Severity is high (CVSS 7.5). 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.

How urgent is CVE-2025-64258?

Priority 39/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2025-68547 HIGH 7.5 UPGRADE Missing Authorization vulnerability in wpweb Follow My Blog Post follow-my-blog-post allows Exploiting Incorre

References

← Back to latest CVEs