How severe is CVE-2009-2569?

CVE-2009-2569 has a CVSS 2.0 base score of 4.3, rated medium severity.

Is CVE-2009-2569 being actively exploited?

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

What products are affected by CVE-2009-2569?

CVE-2009-2569 affects Verlihub-project Verlihub Control Panel. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2009-2569?

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

When was CVE-2009-2569 published?

CVE-2009-2569 was published on 2009-07-22 and last updated on 2026-06-16.

CVE-2009-2569

CVE-2009-2569 is a medium-severity vulnerability in Verlihub-project Verlihub Control Panel with a CVSS 2.0 base score of 4.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-79.

Key facts

Severity: Medium (CVSS 2.0 base score 4.3)
EPSS exploit prediction: 2% (75th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-79
Affected product: Verlihub-project Verlihub Control Panel
Published: 2009-07-22
Last modified: 2026-06-16

Description

Multiple cross-site scripting (XSS) vulnerabilities in Verlihub Control Panel (VHCP) 1.7e allow remote attackers to inject arbitrary web script or HTML via (1) the nick parameter in a login action to index.php or (2) the URI in a news request to index.html.

Frequently asked questions

What is CVE-2009-2569?: Multiple cross-site scripting (XSS) vulnerabilities in Verlihub Control Panel (VHCP) 1.7e allow remote attackers to inject arbitrary web script or HTML via (1) the nick parameter in a login action to index.php or (2) the URI in a news request to index.html.
How severe is CVE-2009-2569?: CVE-2009-2569 has a CVSS 2.0 base score of 4.3, rated medium severity.
Is CVE-2009-2569 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (75th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2009-2569?: CVE-2009-2569 affects Verlihub-project Verlihub Control Panel. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2009-2569?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2009-2569 published?: CVE-2009-2569 was published on 2009-07-22 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:verlihub-project:verlihub_control_panel:1.7e:*:*:*:*:*:*:*

More vulnerabilities in Verlihub-project Verlihub Control Panel

CVE-2007-5321 — Medium (CVSS 6.8): Directory traversal vulnerability in index.php in Verlihub Control Panel (VHCP) 1.7 and earlier allows remote attackers…

All CVEs affecting Verlihub-project Verlihub Control Panel →

Other CWE-79 (Cross-site Scripting (XSS)) vulnerabilities

CVE-2025-49410 — Critical (CVSS 10.0): Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Imran Emu TC…
CVE-2024-47875 — Critical (CVSS 10.0): DOMPurify is a DOM-only, super-fast, uber-tolerant XSS sanitizer for HTML, MathML and SVG. DOMpurify was vulnerable to…
CVE-2024-6886 — Critical (CVSS 10.0): Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Gitea…
CVE-2023-45144 — Critical (CVSS 10.0): com.xwiki.identity-oauth:identity-oauth-ui is a package to aid in building identity and service providers based on…
CVE-2023-45138 — Critical (CVSS 10.0): Change Request is an pplication allowing users to request changes on a wiki without publishing the changes directly.…
CVE-2022-4361 — Critical (CVSS 10.0): Keycloak, an open-source identity and access management solution, has a cross-site scripting (XSS) vulnerability in the…

Browse all CWE-79 (Cross-site Scripting (XSS)) vulnerabilities →