How severe is CVE-2003-1187?

CVE-2003-1187 has a CVSS 2.0 base score of 6.8, rated medium severity.

Is CVE-2003-1187 being actively exploited?

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

What products are affected by CVE-2003-1187?

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

How do I fix CVE-2003-1187?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2003-1187 published?

CVE-2003-1187 was published on 2003-11-02 and last updated on 2026-06-16.

CVE-2003-1187

CVE-2003-1187 is a medium-severity vulnerability in Phpkit with a CVSS 2.0 base score of 6.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 2.0 base score 6.8)
EPSS exploit prediction: 4% (90th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Phpkit
Published: 2003-11-02
Last modified: 2026-06-16

Description

Cross-site scripting (XSS) vulnerability in include.php in PHPKIT 1.6.02 and 1.6.03 allows remote attackers to inject arbitrary web script or HTML via the contact_email parameter.

Frequently asked questions

What is CVE-2003-1187?: Cross-site scripting (XSS) vulnerability in include.php in PHPKIT 1.6.02 and 1.6.03 allows remote attackers to inject arbitrary web script or HTML via the contact_email parameter.
How severe is CVE-2003-1187?: CVE-2003-1187 has a CVSS 2.0 base score of 6.8, rated medium severity.
Is CVE-2003-1187 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (90th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2003-1187?: CVE-2003-1187 primarily affects Phpkit. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2003-1187?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2003-1187 published?: CVE-2003-1187 was published on 2003-11-02 and last updated on 2026-06-16.

References

Affected products (2)

cpe:2.3:a:phpkit:phpkit:1.6.02:*:*:*:*:*:*:*
cpe:2.3:a:phpkit:phpkit:1.6.03:*:*:*:*:*:*:*

More vulnerabilities in Phpkit

CVE-2016-10758 — High (CVSS 8.8): PHPKIT 1.6.6 allows arbitrary File Upload, as demonstrated by a .php file to pkinc/admin/mediaarchive.php and…
CVE-2007-6134 — High (CVSS 7.5): SQL injection vulnerability in pkinc/public/article.php in PHPKIT 1.6.4pl1 allows remote attackers to execute arbitrary…
CVE-2006-7115 — High (CVSS 7.5): SQL injection vulnerability in PHPKit 1.6.1 RC2 allows remote attackers to inject arbitrary SQL commands via the catid…
CVE-2007-0179 — High (CVSS 7.5): SQL injection vulnerability in comment.php in PHPKIT 1.6.1 R2 allows remote attackers to execute arbitrary SQL commands…
CVE-2005-3553 — High (CVSS 7.5): Multiple SQL injection vulnerabilities in include.php in PHPKIT 1.6.1 R2 and earlier allow remote attackers to execute…
CVE-2005-2683 — High (CVSS 7.5): Multiple SQL injection vulnerabilities in PHPKit 1.6.1 allow remote attackers to execute arbitrary SQL commands via the…

All CVEs affecting Phpkit →