What is the severity of CVE-2012-6458?

CVE-2012-6458 is classified as a medium severity vulnerability due to its potential for cross-site scripting attacks.

How do I fix CVE-2012-6458?

To fix CVE-2012-6458, you should update the SilverStripe e-commerce module to a version that has patched this vulnerability.

What are the affected components in CVE-2012-6458?

CVE-2012-6458 affects the SilverStripe e-commerce module 3.0 for SilverStripe CMS, specifically the OrderFormAddress.php file.

Who is impacted by CVE-2012-6458?

Users of SilverStripe CMS who utilize the e-commerce module version 3.0.0 are impacted by CVE-2012-6458.

How can attackers exploit CVE-2012-6458?

Attackers can exploit CVE-2012-6458 by injecting malicious scripts via the FirstName, Surname, or Email parameters in the OrderFormAddress.php file.

Vulnerability/
CVE-2012-6458

medium

4.3

CWE

9/8/2013

3/10/2022

6/8/2024

CVE-2012-6458: XSS

First published: Fri Aug 09 2013(Updated: )

Multiple cross-site scripting (XSS) vulnerabilities in the SilverStripe e-commerce module 3.0 for SilverStripe CMS allow remote attackers to inject arbitrary web script or HTML via the (1) FirstName, (2) Surname, or (3) Email parameter to code/forms/OrderFormAddress.php; or the (4) FirstName or (5) Surname parameter to code/forms/ShopAccountForm.php.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Silverstripe silverstripe	=3.0.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2012-6458?
CVE-2012-6458 is classified as a medium severity vulnerability due to its potential for cross-site scripting attacks.
How do I fix CVE-2012-6458?
To fix CVE-2012-6458, you should update the SilverStripe e-commerce module to a version that has patched this vulnerability.
What are the affected components in CVE-2012-6458?
CVE-2012-6458 affects the SilverStripe e-commerce module 3.0 for SilverStripe CMS, specifically the OrderFormAddress.php file.
Who is impacted by CVE-2012-6458?
Users of SilverStripe CMS who utilize the e-commerce module version 3.0.0 are impacted by CVE-2012-6458.
How can attackers exploit CVE-2012-6458?
Attackers can exploit CVE-2012-6458 by injecting malicious scripts via the FirstName, Surname, or Email parameters in the OrderFormAddress.php file.

collector/nvd-index
agent/references
agent/type
agent/first-publish-date
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/severity
agent/last-modified-date
agent/weakness
agent/tags
agent/description
agent/event
agent/source
vendor/silverstripe
canonical/silverstripe silverstripe
version/silverstripe silverstripe/3.0.0

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-2012-6458?
CVE-2012-6458 is classified as a medium severity vulnerability due to its potential for cross-site scripting attacks.
How do I fix CVE-2012-6458?
To fix CVE-2012-6458, you should update the SilverStripe e-commerce module to a version that has patched this vulnerability.
What are the affected components in CVE-2012-6458?
CVE-2012-6458 affects the SilverStripe e-commerce module 3.0 for SilverStripe CMS, specifically the OrderFormAddress.php file.
Who is impacted by CVE-2012-6458?
Users of SilverStripe CMS who utilize the e-commerce module version 3.0.0 are impacted by CVE-2012-6458.
How can attackers exploit CVE-2012-6458?
Attackers can exploit CVE-2012-6458 by injecting malicious scripts via the FirstName, Surname, or Email parameters in the OrderFormAddress.php file.