What is the CVSS score of CVE-2025-28103?

CVE-2025-28103 has a CVSS 3.1 base score of 6.4 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.2%.

Which versions of Flaskblog are affected by CVE-2025-28103?

Organizations using laskBlog should be aware of moderate risk from CVE-2025-28103, a missing authorization vulnerability rated CVSS 6.4. Attackers could gain access beyond their authorized level.

How to fix or mitigate CVE-2025-28103?

Within 30 days: Identify affected systems running laskBlog and apply vendor patches as part of regular patch cycle. Monitor vendor channels for patch availability.

Flaskblog CVE-2025-28103

MEDIUM

Missing Authorization (CWE-862)

2025-04-21 cve@mitre.org

Authentication Bypass Flaskblog Dogukanurker

6.4

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

6.4 MEDIUM

AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 18:38 vuln.today

CVE Published

Apr 21, 2025 - 18:15 nvd

MEDIUM 6.4

DescriptionCVE.org

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

AnalysisAI

Incorrect access control in laskBlog v2.6.1 allows attackers to arbitrarily delete user accounts via a crafted request. Rated medium severity (CVSS 6.4), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.

Technical ContextAI

This vulnerability is classified as Missing Authorization (CWE-862), which allows attackers to access resources or perform actions without proper authorization checks. Incorrect access control in laskBlog v2.6.1 allows attackers to arbitrarily delete user accounts via a crafted request. Affected products include: Dogukanurker Flaskblog.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Implement role-based access control, validate authorization on every request server-side, apply principle of least privilege.