CVE-2025-55736

CVE-2025-55736 is a medium-severity vulnerability in Dogukanurker Flaskblog with a CVSS 3.x base score of 6.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-425.

Key facts

Description

flaskBlog is a blog app built with Flask. In 2.8.0 and earlier, an arbitrary user can change his role to "admin", giving its relative privileges (e.g. delete users, posts, comments etc.). The problem is in the routes/adminPanelUsers file.

Frequently asked questions

What is CVE-2025-55736?
flaskBlog is a blog app built with Flask. In 2.8.0 and earlier, an arbitrary user can change his role to "admin", giving its relative privileges (e.g. delete users, posts, comments etc.). The problem is in the routes/adminPanelUsers file.
How severe is CVE-2025-55736?
CVE-2025-55736 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2025-55736 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (16th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-55736?
CVE-2025-55736 affects Dogukanurker Flaskblog. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-55736?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-55736 have an EU (EUVD) identifier?
Yes. CVE-2025-55736 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-28607.
When was CVE-2025-55736 published?
CVE-2025-55736 was published on 2025-08-19 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Dogukanurker Flaskblog

All CVEs affecting Dogukanurker Flaskblog →

Other CWE-425 vulnerabilities

Browse all CWE-425 vulnerabilities →