CVE-2022-24374: XSS

Published Feb 24, 2022
·
Updated

Cross-site scripting vulnerability in a-blog cms Ver.2.8.x series versions prior to Ver.2.8.75, Ver.2.9.x series versions prior to Ver.2.9.40, Ver.2.10.x series versions prior to Ver.2.10.44, Ver.2.11.x series versions prior to Ver.2.11.42, and Ver.3.0.x series versions prior to Ver.3.0.1 allows a remote authenticated attacker to inject an arbitrary script via unspecified vectors. This vulnerability is different from CVE-2022-23916.

Affected Software

5 affected components
Appleple a-blog cms>=2.8.0<2.8.75
Appleple a-blog cms>=2.9.0<2.9.40
Appleple a-blog cms>=2.10.0<2.10.44
Appleple a-blog cms>=2.11.0<2.11.42
Appleple a-blog cms=3.0.0

Event History

Feb 24, 2022
CVE Published
via MITRE·09:50 AM
Data Sourced
via MITRE·09:50 AM
DescriptionWeakness

Frequently Asked Questions

1

What is the severity of CVE-2022-24374?

CVE-2022-24374 is classified as a cross-site scripting (XSS) vulnerability that can lead to significant security risks for affected systems.

2

How do I fix CVE-2022-24374?

To mitigate CVE-2022-24374, update a-blog cms to version 2.8.75 or higher, 2.9.40 or higher, 2.10.44 or higher, 2.11.42 or higher, or 3.0.1 or higher.

3

What versions of a-blog cms are affected by CVE-2022-24374?

CVE-2022-24374 affects a-blog cms versions 2.8.x before 2.8.75, 2.9.x before 2.9.40, 2.10.x before 2.10.44, 2.11.x before 2.11.42, and 3.0.x before 3.0.1.

4

What type of vulnerability is CVE-2022-24374?

CVE-2022-24374 is a cross-site scripting (XSS) vulnerability that can allow an attacker to inject malicious scripts into web pages.

5

Who is affected by CVE-2022-24374?

Any user of the specified vulnerable versions of a-blog cms may be affected by CVE-2022-24374 if they do not update to the recommended secure versions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203