How severe is CVE-2005-3519?

CVE-2005-3519 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2005-3519 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 8% (94th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2005-3519?

CVE-2005-3519 primarily affects Mysource. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2005-3519?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2005-3519 published?

CVE-2005-3519 was published on 2005-11-06 and last updated on 2026-06-16.

CVE-2005-3519

CVE-2005-3519 is a high-severity vulnerability in Mysource with a CVSS 2.0 base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 2.0 base score 7.5)
EPSS exploit prediction: 8% (94th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Mysource
Published: 2005-11-06
Last modified: 2026-06-16

Description

Multiple PHP file inclusion vulnerabilities in MySource 2.14.0 allow remote attackers to execute arbitrary PHP code and include arbitrary local files via the (1) INCLUDE_PATH and (2) SQUIZLIB_PATH parameters in new_upgrade_functions.php, (3) the INCLUDE_PATH parameter in init_mysource.php, and the PEAR_PATH parameter in (4) Socket.php, (5) Request.php, (6) Mail.php, (7) Date.php, (8) Span.php, (9) mimeDecode.php, and (10) mime.php.

Frequently asked questions

What is CVE-2005-3519?: Multiple PHP file inclusion vulnerabilities in MySource 2.14.0 allow remote attackers to execute arbitrary PHP code and include arbitrary local files via the (1) INCLUDE_PATH and (2) SQUIZLIB_PATH parameters in new_upgrade_functions.php, (3) the INCLUDE_PATH parameter in init_mysource.php, and the PEAR_PATH parameter in (4) Socket.php, (5) Request.php, (6) Mail.php, (7) Date.php, (8) Span.php, (9) mimeDecode.php, and (10) mime.php.
How severe is CVE-2005-3519?: CVE-2005-3519 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2005-3519 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 8% (94th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-3519?: CVE-2005-3519 primarily affects Mysource. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2005-3519?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2005-3519 published?: CVE-2005-3519 was published on 2005-11-06 and last updated on 2026-06-16.

References

Affected products (2)

cpe:2.3:a:mysource:mysource:2.14.0:*:*:*:*:*:*:*
cpe:2.3:a:mysource:mysource:2.14.0rc2:*:*:*:*:*:*:*

More vulnerabilities in Mysource

CVE-2005-3520 — Medium (CVSS 4.3): Multiple cross-site scripting (XSS) vulnerabilities in MySource 2.14.0 allow remote attackers to inject arbitrary web…

All CVEs affecting Mysource →