Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

a-blogcms vulnerabilities and fixes

Recent CVEs affecting a-blogcms, with upgrade or downgrade steps. 1 tracked.

Also searched as: a blogcms.

a-blogcms has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2025-04-17. Highest priority: CVE-2025-29461 (score 41/100).

FAQ

How do I fix a-blogcms vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is a-blogcms being exploited right now?

None of the tracked a-blogcms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which a-blogcms CVE should I patch first?

CVE-2025-29461 currently ranks highest (41/100): An issue in a-blogcms 3.1.15 allows a remote attacker to obtain sensitive information via the /bid/1/admin/ent.

← Back to latest CVEs