CVE-2012-2058: Medium severity paypal payflow vulnerability

Published Sep 17, 2012
·
Updated

The Ubercart Payflow module for Drupal does not use a secure token, which allows remote attackers to forge payments via unspecified vectors.

Affected Software

2 affected components
Paypal Ubercart Payflow
Drupal Drupal

Event History

Sep 17, 2012
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2012-2058?

CVE-2012-2058 is considered a medium severity vulnerability due to its ability to allow remote attackers to forge payments.

2

How do I fix CVE-2012-2058?

To fix CVE-2012-2058, update the Ubercart Payflow module to the latest version that implements secure token usage.

3

Who is affected by CVE-2012-2058?

CVE-2012-2058 affects users of the Ubercart Payflow module for Drupal that do not utilize secure tokens.

4

What kind of attack can be performed using CVE-2012-2058?

CVE-2012-2058 allows attackers to forge payments by exploiting the lack of a secure token in the transaction process.

5

Is there a workaround for CVE-2012-2058 if I cannot update?

Currently, the only recommendation for CVE-2012-2058 is to implement updates as there are no reliable workarounds to mitigate the vulnerability.

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