CVE-2018-6379: XSS

Q: What must an attacker do to exploit this issue?

An attacker must cause a user to interact with malicious content, as reflected by the required user interaction in the CVSS vector. The issue is network-reachable and requires no attacker privileges.

Q: What security impact can successful exploitation have?

Successful exploitation can lead to limited disclosure and modification of information. The CVSS vector indicates the impact scope can extend beyond the vulnerable component, while availability is not affected.

Q: Which Joomla! versions need remediation?

Joomla! versions before 3.8.4 are affected. Upgrade to 3.8.4 or a later version.

Published Jan 30, 2018

Updated

In Joomla! before 3.8.4, inadequate input filtering in the Uri class (formerly JUri) leads to an XSS vulnerability.

Affected Software

1 affected component

Joomla Joomla\!<3.8.4

Event History

Jan 30, 2018

CVE Published

via MITRE·05:00 PM

Data Sourced

via MITRE·05:00 PM

Description

Data Sourced

via NVD·05:29 PM

DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

What must an attacker do to exploit this issue?

An attacker must cause a user to interact with malicious content, as reflected by the required user interaction in the CVSS vector. The issue is network-reachable and requires no attacker privileges.

What security impact can successful exploitation have?

Successful exploitation can lead to limited disclosure and modification of information. The CVSS vector indicates the impact scope can extend beyond the vulnerable component, while availability is not affected.

Which Joomla! versions need remediation?

Joomla! versions before 3.8.4 are affected. Upgrade to 3.8.4 or a later version.

CVE-2018-6379: XSS

Affected Software

Event History

Frequently Asked Questions

What must an attacker do to exploit this issue?

What security impact can successful exploitation have?

Which Joomla! versions need remediation?

Company

Resources

Contact

Frequently Asked Questions

What must an attacker do to exploit this issue?

What security impact can successful exploitation have?

Which Joomla! versions need remediation?