a-blog cms vulnerabilities and fixes

Recent CVEs affecting a-blog cms, with upgrade or downgrade steps. 5 tracked.

Also searched as: a blog cms, a-blogcms.

a-blog cms has 5 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 5. Most recent: 2025-05-19. Highest priority: CVE-2025-36560 (score 46/100).

• CVE-2025-41429 MEDIUM 4.8 UPGRADE a-blog cms multiple versions neutralize logs improperly
• CVE-2025-36560 HIGH 8.6 UPGRADE Server-side request forgery vulnerability exists in a-blog cms multiple versions
• CVE-2025-32999 MEDIUM 5.4 UPGRADE Cross-site scripting vulnerability exists in a-blog cms versions prior to Ver
• CVE-2025-31103 HIGH 7.5 UPGRADE Untrusted data deserialization vulnerability exists in a-blog cms
• CVE-2025-27566 LOW 3.8 UPGRADE Path traversal vulnerability exists in a-blog cms versions prior to Ver

FAQ

How do I fix a-blog cms 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-blog cms being exploited right now?

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

Which a-blog cms CVE should I patch first?

CVE-2025-36560 currently ranks highest (46/100): Server-side request forgery vulnerability exists in a-blog cms multiple versions.

RSS feed for a-blog cms · ← Back to latest CVEs