CVE-2007-5934: Infoleak

Published Nov 13, 2007
·
Updated

The LOB functionality in PEAR MDB2 before 2.5.0a1 interprets a request to store a URL string as a request to retrieve and store the contents of the URL, which might allow remote attackers to use MDB2 as an indirect proxy or obtain sensitive information via a URL into a form field in an MDB2 application, as demonstrated by a file:// URL or a URL for an intranet web site.

Affected Software

1 affected component
PEAR Structures Datagrid Datasource Mdb2<=2.5.0

Event History

Nov 13, 2007
CVE Published
via MITRE·10:00 PM
Data Sourced
via MITRE·10:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2007-5934?

CVE-2007-5934 is classified as a moderate severity vulnerability due to its potential for unauthorized access to sensitive information.

2

How do I fix CVE-2007-5934?

To fix CVE-2007-5934, upgrade to PEAR MDB2 version 2.5.0a1 or later.

3

What is the impact of CVE-2007-5934?

CVE-2007-5934 could allow remote attackers to leverage the MDB2 framework to act as an indirect proxy or access sensitive data.

4

Which versions of PEAR MDB2 are affected by CVE-2007-5934?

PEAR MDB2 versions prior to 2.5.0a1 are affected by CVE-2007-5934.

5

Is CVE-2007-5934 still a risk today?

The risk from CVE-2007-5934 is minimized if systems are patched; however, unpatched systems may still be vulnerable.

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