Skip to main content
VulnerabilityPublished Updated

CVE-2025-68547: Follow My Blog Post (WordPress plugin) · Missing Authorization

Affects Follow My Blog Post (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 7.5 High : upgrade to 2.4.1 soon.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.4.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Follow My Blog Post (WordPress plugin) to 2.4.1.

Affected software

ProductAffectedFixed in
wpwebFollow My Blog PostAffected
  • <2.4.1
Fixed in
  • 2.4.1

AI-suggested

If you cannot patch yet, restrict access to the plugin's functionalities where possible and monitor for unusual activity related to this plugin. Avoid exposing the plugin to untrusted networks or users.

Description

Missing Authorization vulnerability in wpweb Follow My Blog Post follow-my-blog-post allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Follow My Blog Post: from n/a through <= 2.4.0.

References

Community reviews

Loading reviews…