CVE-2025-2339: A vulnerability was found in otale Tale Blog 2.0.5

This week

MEDIUM 5.3REMOTEDOWNGRADE

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

A vulnerability was found in otale Tale Blog 2.0.5. It has been classified as problematic. This affects an unknown part of the file /%61dmin/api/logs. The manipulation leads to improper authentication. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way. This vulnerability only affects products that are no

Why this priority

Public exploit reference
Remotely exploitable, no login, no user action

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

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.9% (top 39%)
CISA exploited list	No
Weakness	CWE-287
Published	2025-03-16
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: otale

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

Am I affected?

Timeline

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

otale tale blog DOWNGRADE

Affected: 2.0.5

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0.5

1. Check installed version

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

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

apt-cache madison tale-blog sudo apt install tale-blog=<VERSION_BEFORE_2.0.5> sudo apt-mark hold tale-blog

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

dnf --showduplicates list tale-blog sudo dnf downgrade tale-blog-<VERSION_BEFORE_2.0.5> sudo dnf versionlock add tale-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-2339?

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

Is CVE-2025-2339 being exploited?

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

CVE-2025-2339 affects tale blog. Severity is medium (CVSS 5.3). A vulnerability was found in otale Tale Blog 2.0.5. It has been classified as problematic. This affects an unknown part of the file /%61dmin/api/logs. The manipulation leads to improper authentication. It is possible to initiate the attack

How urgent is CVE-2025-2339?

Priority 44/100. Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2025-2340 LOW 2.4 DOWNGRADE A vulnerability was found in otale Tale Blog 2.0.5

References

← Back to latest CVEs