What is the severity of CVE-2018-16372?

CVE-2018-16372 is classified as a reflected cross-site scripting (XSS) vulnerability.

How does CVE-2018-16372 work?

CVE-2018-16372 allows an attacker to execute arbitrary JavaScript in the context of a user's browser through a crafted kw parameter in the search functionality.

How do I fix CVE-2018-16372?

There is no official fix available for CVE-2018-16372 since IdeaCMS is a discontinued product, so migration to a different CMS is recommended.

Is CVE-2018-16372 still a threat today?

CVE-2018-16372 remains a threat if the affected software is still in use and does not have proper mitigating controls in place.

What can be done to mitigate CVE-2018-16372?

To mitigate CVE-2018-16372, implement web application firewall rules to block XSS attempts and validate or sanitize user input.

Vulnerability/
CVE-2018-16372

medium

6.1

CWE

3/9/2018

5/8/2024

CVE-2018-16372: XSS

First published: Mon Sep 03 2018(Updated: )

The issue was discovered in IdeaCMS through 2016-04-30. There is reflected XSS via the index.php?c=content&a=search kw parameter. NOTE: this product is discontinued.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Ideacms	<=2016-04-30

Never miss a vulnerability like this again

Reference Links

https://github.com/iechoo/ideacms/issues/1

Frequently Asked Questions

What is the severity of CVE-2018-16372?
CVE-2018-16372 is classified as a reflected cross-site scripting (XSS) vulnerability.
How does CVE-2018-16372 work?
CVE-2018-16372 allows an attacker to execute arbitrary JavaScript in the context of a user's browser through a crafted kw parameter in the search functionality.
How do I fix CVE-2018-16372?
There is no official fix available for CVE-2018-16372 since IdeaCMS is a discontinued product, so migration to a different CMS is recommended.
Is CVE-2018-16372 still a threat today?
CVE-2018-16372 remains a threat if the affected software is still in use and does not have proper mitigating controls in place.
What can be done to mitigate CVE-2018-16372?
To mitigate CVE-2018-16372, implement web application firewall rules to block XSS attempts and validate or sanitize user input.

agent/type
collector/mitre-cve
source/MITRE
agent/severity
agent/references
agent/last-modified-date
agent/author
agent/description
agent/first-publish-date
agent/event
agent/source
agent/weakness
agent/softwarecombine
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/ideacms
canonical/ideacms
version/ideacms/2016-04-30

Company

Resources

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.

Frequently Asked Questions

What is the severity of CVE-2018-16372?
CVE-2018-16372 is classified as a reflected cross-site scripting (XSS) vulnerability.
How does CVE-2018-16372 work?
CVE-2018-16372 allows an attacker to execute arbitrary JavaScript in the context of a user's browser through a crafted kw parameter in the search functionality.
How do I fix CVE-2018-16372?
There is no official fix available for CVE-2018-16372 since IdeaCMS is a discontinued product, so migration to a different CMS is recommended.
Is CVE-2018-16372 still a threat today?
CVE-2018-16372 remains a threat if the affected software is still in use and does not have proper mitigating controls in place.
What can be done to mitigate CVE-2018-16372?
To mitigate CVE-2018-16372, implement web application firewall rules to block XSS attempts and validate or sanitize user input.