CVE-2025-8740: A vulnerability was found in zhenfeng13 My-Blog up to 1.0.0

Routine

LOW 2.4DOWNGRADE

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

A vulnerability was found in zhenfeng13 My-Blog up to 1.0.0. It has been classified as problematic. Affected is an unknown function of the file /admin/categories/save of the component Category Handler. The manipulation of the argument categoryName leads to cross site scripting. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	2.4 (Low)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	Required
EPSS exploit chance	0.3% (top 77%)
CISA exploited list	No
Weakness	CWE-79, CWE-94
Published	2025-08-08
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: zhenfeng13

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

Am I affected?

Timeline

2025-08-08 21:15 UTCPublished CVE record published
2026-06-17 10:07 UTCUpdated Record last modified

zhenfeng13 my-blog DOWNGRADE

Affected: 1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0

1. Check installed version

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

2. No fixed release: DOWNGRADE to a release before 1.0 (Debian / Ubuntu)

apt-cache madison my-blog sudo apt install my-blog=<VERSION_BEFORE_1.0> sudo apt-mark hold my-blog

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list my-blog sudo dnf downgrade my-blog-<VERSION_BEFORE_1.0> sudo dnf versionlock add my-blog

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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-8740?

my-blog: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-8740 being exploited?

CVE-2025-8740 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-8740 affect?

CVE-2025-8740 affects my-blog. Severity is low (CVSS 2.4). A vulnerability was found in zhenfeng13 My-Blog up to 1.0.0. It has been classified as problematic. Affected is an unknown function of the file /admin/categories/save of the component Category Handler. The manipulation of the argument categ

How urgent is CVE-2025-8740?

Priority 19/100. Public exploit reference

Related CVEs

CVE-2025-8739 MEDIUM 4.3 DOWNGRADE A vulnerability was found in zhenfeng13 My-Blog up to 1.0.0 and classified as problematic
CVE-2024-13145 MEDIUM 6.3 DOWNGRADE A vulnerability classified as critical was found in zhenfeng13 My-Blog 1.0
CVE-2024-13144 MEDIUM 6.3 DOWNGRADE A vulnerability classified as critical has been found in zhenfeng13 My-Blog 1.0

References

← Back to latest CVEs