CVE-2024-23782VulnerabilityPublished 28 Jan 2024Updated 2 Jun 2025

CVE-2024-23782: appleple a-blog cms Ver.3.1.x series · Cross-site Scripting (XSS)

Affects appleple a-blog cms Ver.3.1.x seriesSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium · fixed in 3.1.7 : update appleple a-blog cms Ver.3.1.x series when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 22% 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 +2

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
appleple inc. a-blog cms Ver.3.1.x series	Affected <3.1.7 <2.9.1 <2.10.50 <2.11.58 <3.0.29	Fixed in 3.1.7 2.9.1 2.10.50 2.11.58 3.0.29

AI-suggested

1. Immediate upgrade: Organizations should promptly update a-blog cms installations to version 3.1.7 or later (or the corresponding fixed versions for other series) to remediate the vulnerability. 2. Privilege review: Conduct an audit of user roles and permissions within the CMS to ensure that contributor or higher privileges are only granted to trusted users. Limit the number of users with such privileges. 3. Input validation and output encoding: Implement additional web application firewall (WAF) rules to detect and block suspicious script injections targeting the CMS. 4. Content security policy (CSP): Deploy strict CSP headers to restrict the execution of unauthorized scripts in browsers accessing the CMS-managed sites. 5. User awareness: Educate contributors and administrators about the risks of XSS and safe content handling practices. 6. Monitoring and logging: Enable detailed logging of CMS activities and monitor for unusual behavior or injection attempts. 7. Segmentation: Isolate the CMS environment from critical internal networks to limit lateral movement if exploitation occurs. 8. Incident response readiness: Prepare to respond to potential incidents involving XSS exploitation, including session hijacking or website defacement.

Description

Cross-site scripting vulnerability exists 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 versions. If this vulnerability is exploited, a user with a contributor or higher privilege may execute an arbitrary script on the web browser of the user who accessed the website using the product.

Impact

For European organizations using a-blog cms, this vulnerability poses a moderate risk. Since the attack requires contributor or higher privileges, the threat is primarily from insiders or attackers who have already gained some level of access. Exploitation can lead to theft of sensitive information such as session cookies, user credentials, or other confidential data accessible via the browser. It can also enable attackers to perform unauthorized actions within the CMS, potentially defacing websites, injecting malware, or pivoting to other internal systems. Given that a-blog cms is a content management system, organizations relying on it for public-facing websites or intranet portals may face reputational damage, data leakage, and disruption of services. The medium CVSS score reflects that while the vulnerability is not trivial, it is not easily exploitable by unauthenticated attackers, somewhat limiting its impact. However, the scope change indicates that the impact can extend beyond the immediate vulnerable component, increasing the risk. European organizations in sectors such as media, education, government, and SMEs that use this CMS should be particularly vigilant, as these sectors often use CMS platforms extensively and may have contributors with elevated privileges.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Jul 2025, 18:10 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats