- Vulnerability/
- CVE-2025-28103
CVE-2025-28103
First published: Mon Apr 21 2025(Updated: )
Incorrect access control in laskBlog v2.6.1 allows attackers to arbitrarily delete user accounts via a crafted request.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| laskBlog |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2025-28103?
CVE-2025-28103 has been classified as a critical severity vulnerability due to its potential to allow unauthorized account deletions.
How do I fix CVE-2025-28103?
To fix CVE-2025-28103, update to the latest version of laskBlog where the access control issue has been addressed.
What are the consequences of exploiting CVE-2025-28103?
Exploiting CVE-2025-28103 could lead to complete account loss for users as attackers can delete user accounts without authorization.
Which versions of laskBlog are affected by CVE-2025-28103?
CVE-2025-28103 affects laskBlog version 2.6.1 specifically.
What type of vulnerability is CVE-2025-28103?
CVE-2025-28103 is an access control vulnerability that allows attackers to perform unauthorized actions.
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/type
- agent/description
- agent/first-publish-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/author
- agent/last-modified-date
- agent/source
- agent/tags
- agent/event
- vendor/laskblog
- canonical/laskblog