LiveActive security incident?Get immediate response
CVE Record

CVE-2007-5934: The LOB functionality in PEAR MDB2 before 2.5.0a1 interprets a request to store a URL string as a request t...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This flaw affects old PEAR MDB2 versions used by PHP applications. When an application stores large objects, MDB2 may treat a submitted URL as something to fetch, not plain text. An attacker could make the server retrieve local files or internal web resources if the application accepts such input. Exposure is likely limited to legacy PHP applications using PEAR MDB2 before 2.5.0a1 with LOB functionality reachable through user-controlled form fields or API inputs. Systems without PEAR MDB2, without LOB use, or without attacker-controlled LOB input are less likely exposed. Prioritize if legacy PHP applications use PEAR MDB2 and accept user-submitted file, document, or rich content fields. The issue can expose internal resources, but evidence in the provided sources does not indicate active exploitation. Treat as a targeted legacy dependency remediation task. Mitigation focus: Upgrade PEAR MDB2 to 2.5.0a1 or later where applicable.; Apply distribution vendor updates for packaged PEAR MDB2 installations.; Restrict user-controlled input from reaching MDB2 LOB storage paths..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2007-5934 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.