CVE-2025-3004: A vulnerability has been found in Sayski ForestBlog up to 20250321 and classified as problematic

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

forestblog: upgrade to 2025-03-21. Exact commands for each OS are on this page.

Q: Is CVE-2025-3004 being exploited?

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

CVE-2025-3004 affects forestblog. Severity is low (CVSS 3.5). A vulnerability has been found in Sayski ForestBlog up to 20250321 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file /search. The manipulation of the argument keywords leads to cross site

Q: How urgent is CVE-2025-3004?

Priority 24/100. Public exploit reference

Routine

LOW 3.5UPGRADE

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

A vulnerability has been found in Sayski ForestBlog up to 20250321 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file /search. The manipulation of the argument keywords leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

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

Publisher (CNA): VulDB · Vendor: forestblog project

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

Am I affected?

Timeline

2025-03-31 17:15 UTCPublished CVE record published
2026-06-17 09:18 UTCUpdated Record last modified

forestblog project forestblog UPGRADE

Affected: < 2025-03-21

Fixed in: 2025-03-21

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy forestblog || rpm -q forestblog || forestblog --version

2. UPGRADE to 2025-03-21 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade forestblog

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade forestblog

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

forestblog: upgrade to 2025-03-21. Exact commands for each OS are on this page.

Is CVE-2025-3004 being exploited?

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

CVE-2025-3004 affects forestblog. Severity is low (CVSS 3.5). A vulnerability has been found in Sayski ForestBlog up to 20250321 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file /search. The manipulation of the argument keywords leads to cross site

How urgent is CVE-2025-3004?

Priority 24/100. Public exploit reference

Related CVEs

CVE-2025-3005 LOW 3.5 UPGRADE A vulnerability was found in Sayski ForestBlog up to 20250321 and classified as problematic
CVE-2024-57498 MEDIUM 4.8 DOWNGRADE Cross Site Scripting vulnerability in sayski ForestBlog 20241223 allows a remote attacker to escalate privileg

References

← Back to latest CVEs