CVE-2024-23182: appleple a-blog cms Ver.3.1.x series · Relative path traversal
Affects appleple a-blog cms Ver.3.1.x seriesSource CVE Database V5
Not known to be exploited · CVSS 8.1 High · fixed in 3.1.7 : patch appleple a-blog cms Ver.3.1.x series soon.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.1.7, 3.0.29, 2.11.58 +1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 23 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade appleple a-blog cms Ver.3.1.x series to 3.1.7, 3.0.29, 2.11.58 or 2.10.50.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| appleple inc. a-blog cms Ver.3.1.x series | Affected
| Fixed in
|
AI-suggested
European organizations should immediately identify all instances of a-blog cms in their environment and verify the version in use. Upgrading to the latest patched versions (3.1.7 or later for the 3.1.x series, and corresponding patched versions for other series) is the most effective mitigation. If immediate upgrade is not feasible, organizations should restrict access to the CMS administration interfaces to trusted networks and users only, employing network segmentation and strict access controls. Implement multi-factor authentication (MFA) to reduce the risk of credential compromise. Conduct thorough audits of user accounts and permissions to ensure that only necessary users have authenticated access. Monitor logs for unusual file deletion activities or other suspicious behavior indicative of exploitation attempts. Employ web application firewalls (WAFs) with custom rules to detect and block path traversal patterns targeting the CMS. Regular backups of CMS files and configurations should be maintained to enable rapid recovery in case of file deletion. Finally, organizations should stay informed via vendor advisories and security bulletins to apply patches promptly once available.
Description
Relative path traversal vulnerability in a-blog cms Ver.3.1.x series versions prior to Ver.3.1.7, Ver.3.0.x series versions prior to Ver.3.0.29, Ver.2.11.x series versions prior to Ver.2.11.58, Ver.2.10.x series versions prior to Ver.2.10.50, and Ver.2.9.0 and earlier allows a remote authenticated attacker to delete arbitrary files on the server.