CVE-2025-36560 Details
Description
Server-side request forgery vulnerability exists in a-blog cms multiple versions. If this vulnerability is exploited, a remote unauthenticated attacker may gain access to sensitive information by sending a specially crafted request.
A server-side request forgery (SSRF) vulnerability has been identified in a-blog cms, affecting multiple versions. This vulnerability allows remote, unauthenticated attackers to access sensitive information by sending specially crafted requests.
Users are advised to update a-blog cms to the latest version. For versions 3.1.43 and earlier, 3.0.47 and earlier, and 2.11.75 and earlier, specific update instructions can be found on the a-blog cms developer site. Additionally, a workaround is available by setting 'HOOK_ENABLE' to '1' in 'config.server.php' and modifying 'extension/acms/Hook.php' or 'php/ACMS/User/Hook.php'.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed May 19, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://developer.a-blogcms.jp/blog/news/JVNVU-90760614.html | [email protected] | Vendor Advisory |
| https://jvn.jp/en/vu/JVNVU90760614/ | [email protected] | Third Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-918 | Server-Side Request Forgery (SSRF) | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| appleple a-blog cms | >= 2.8.0, <= 2.8.85 >= 2.9.0, <= 2.9.52 >= 2.10.0, <= 2.10.63 >= 2.11.0, <= 2.11.75 >= 3.0.0, <= 3.0.47 >= 3.1.0, <= 3.1.43 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Sep 30, 2025 | Initial Analysis | [email protected] |
| May 19, 2025 | New CVE Received | [email protected] |