CVE-2025-28103: Incorrect access control in laskBlog v2.6.1 allows attackers to arbitrarily delete user accounts via a crafted

Routine

MEDIUM 6.4DOWNGRADE

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

Incorrect access control in laskBlog v2.6.1 allows attackers to arbitrarily delete user accounts via a crafted request.

Why this priority

No elevated risk signals yet

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

Risk facts

CVSS score	6.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 87%)
CISA exploited list	No
Weakness	CWE-862
Published	2025-04-21
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: dogukanurker

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

Am I affected?

Timeline

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

dogukanurker flaskblog DOWNGRADE

Affected: 2.6.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.6.1

1. Check installed version

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

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

apt-cache madison flaskblog sudo apt install flaskblog=<VERSION_BEFORE_2.6.1> sudo apt-mark hold flaskblog

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

dnf --showduplicates list flaskblog sudo dnf downgrade flaskblog-<VERSION_BEFORE_2.6.1> sudo dnf versionlock add flaskblog

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

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

Is CVE-2025-28103 being exploited?

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

CVE-2025-28103 affects flaskblog. Severity is medium (CVSS 6.4). Incorrect access control in laskBlog v2.6.1 allows attackers to arbitrarily delete user accounts via a crafted request.

How urgent is CVE-2025-28103?

Priority 26/100. No elevated risk signals yet.

Related CVEs

CVE-2025-55737 MEDIUM 6.5 UPGRADE flaskBlog is a blog app built with Flask
CVE-2025-55736 MEDIUM 6.5 UPGRADE flaskBlog is a blog app built with Flask
CVE-2025-55735 MEDIUM 5.4 UPGRADE flaskBlog is a blog app built with Flask
CVE-2025-55734 MEDIUM 6.5 UPGRADE flaskBlog is a blog app built with Flask
CVE-2025-53631 MEDIUM 5.4 UPGRADE flaskBlog is a blog app built with Flask

References

← Back to latest CVEs