What is the severity of CVE-2019-18982?

CVE-2019-18982 has been classified as a medium severity vulnerability.

How do I fix CVE-2019-18982?

To fix CVE-2019-18982, upgrade to Pimcore version 6.3.0 or later.

What types of attacks can exploit CVE-2019-18982?

CVE-2019-18982 can be exploited to execute malicious scripts through the Email Log preview window.

Which versions of Pimcore are affected by CVE-2019-18982?

Pimcore versions prior to 6.3.0 are affected by CVE-2019-18982.

Is a Content-Security-Policy header required to mitigate CVE-2019-18982?

Yes, implementing a Content-Security-Policy header is necessary to mitigate CVE-2019-18982.

Vulnerability/
CVE-2019-18982

medium

6.1

CWE

15/11/2019

24/5/2022

5/8/2024

CVE-2019-18982: XSS

First published: Fri Nov 15 2019(Updated: )

`bundles/AdminBundle/Controller/Admin/EmailController.php` in Pimcore before 6.3.0 allows script execution in the Email Log preview window because of the lack of a Content-Security-Policy header.

Credit: cve@mitre.org cve@mitre.org

Affected Software	Affected Version	How to fix
Pimcore Pimcore	>=6.0.0<6.3.0
composer/pimcore/pimcore	<6.3.0	6.3.0
	>=6.0.0<6.3.0

Remedy

https://github.com/pimcore/pimcore/commit/e0b48faf7d29ce43a98825a0b230e88350ebcf78

Remedy

https://github.com/pimcore/pimcore/compare/v6.2.3...v6.3.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-18982?
CVE-2019-18982 has been classified as a medium severity vulnerability.
How do I fix CVE-2019-18982?
To fix CVE-2019-18982, upgrade to Pimcore version 6.3.0 or later.
What types of attacks can exploit CVE-2019-18982?
CVE-2019-18982 can be exploited to execute malicious scripts through the Email Log preview window.
Which versions of Pimcore are affected by CVE-2019-18982?
Pimcore versions prior to 6.3.0 are affected by CVE-2019-18982.
Is a Content-Security-Policy header required to mitigate CVE-2019-18982?
Yes, implementing a Content-Security-Policy header is necessary to mitigate CVE-2019-18982.

collector/nvd-index
agent/type
agent/remedy
collector/github-advisory-latest
source/GitHub
alias/GHSA-m4x3-xmjv-r778
alias/CVE-2019-18982
agent/software-canonical-lookup
agent/severity
agent/references
agent/weakness
agent/description
agent/author
agent/softwarecombine
collector/nvd-cve
source/NVD
collector/github-advisory
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/trending
agent/tags
agent/source
vendor/pimcore
canonical/pimcore pimcore
version/pimcore pimcore/6.0.0
package-manager/composer

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-2019-18982?
CVE-2019-18982 has been classified as a medium severity vulnerability.
How do I fix CVE-2019-18982?
To fix CVE-2019-18982, upgrade to Pimcore version 6.3.0 or later.
What types of attacks can exploit CVE-2019-18982?
CVE-2019-18982 can be exploited to execute malicious scripts through the Email Log preview window.
Which versions of Pimcore are affected by CVE-2019-18982?
Pimcore versions prior to 6.3.0 are affected by CVE-2019-18982.
Is a Content-Security-Policy header required to mitigate CVE-2019-18982?
Yes, implementing a Content-Security-Policy header is necessary to mitigate CVE-2019-18982.