CVE-2008-3268

CVE-2008-3268 is a medium-severity vulnerability in Brickhost Phpscheduleit 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. The underlying weakness is classified as CWE-264.

Key facts

Description

Unspecified vulnerability in phpScheduleIt 1.2.0 through 1.2.9, when useLogonName is enabled, allows remote attackers with administrator email address knowledge to bypass restrictions and gain privileges via unspecified vectors related to login names. NOTE: some of these details are obtained from third party information.

Frequently asked questions

What is CVE-2008-3268?
Unspecified vulnerability in phpScheduleIt 1.2.0 through 1.2.9, when useLogonName is enabled, allows remote attackers with administrator email address knowledge to bypass restrictions and gain privileges via unspecified vectors related to login names. NOTE: some of these details are obtained from third party information.
How severe is CVE-2008-3268?
CVE-2008-3268 has a CVSS 2.0 base score of 6.8, rated medium severity.
Is CVE-2008-3268 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (77th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2008-3268?
CVE-2008-3268 primarily affects Brickhost Phpscheduleit. In total, 11 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2008-3268?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2008-3268 published?
CVE-2008-3268 was published on 2008-07-24 and last updated on 2026-06-16.

References

Affected products (11)

More vulnerabilities in Brickhost Phpscheduleit

All CVEs affecting Brickhost Phpscheduleit →

Other CWE-264 (Permissions, Privileges, and Access Controls) vulnerabilities

Browse all CWE-264 (Permissions, Privileges, and Access Controls) vulnerabilities →