How severe is CVE-2005-1499?

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

Is CVE-2005-1499 being actively exploited?

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

What products are affected by CVE-2005-1499?

CVE-2005-1499 primarily affects Mywebland Mybloggie. 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-1499?

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-1499 published?

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

CVE-2005-1499

CVE-2005-1499 is a high-severity vulnerability in Mywebland Mybloggie 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: 3% (84th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Mywebland Mybloggie
Published: 2005-05-11
Last modified: 2026-06-16

Description

delcomment.php in myBloggie 2.1.1 allows remote attackers to delete arbitrary comments by modifying the comment_id parameter.

Frequently asked questions

What is CVE-2005-1499?: delcomment.php in myBloggie 2.1.1 allows remote attackers to delete arbitrary comments by modifying the comment_id parameter.
How severe is CVE-2005-1499?: CVE-2005-1499 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2005-1499 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (84th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-1499?: CVE-2005-1499 primarily affects Mywebland Mybloggie. 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-1499?: 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-1499 published?: CVE-2005-1499 was published on 2005-05-11 and last updated on 2026-06-16.

References

Affected products (2)

cpe:2.3:a:mywebland:mybloggie:2.1.1:*:*:*:*:*:*:*
cpe:2.3:a:mywebland:mybloggie:2.1.2:*:*:*:*:*:*:*

More vulnerabilities in Mywebland Mybloggie

CVE-2007-3194 — Critical (CVSS 9.8): Multiple PHP remote file inclusion vulnerabilities in myBloggie 2.1.5 allow remote attackers to execute arbitrary PHP…
CVE-2007-3003 — High (CVSS 7.5): Multiple SQL injection vulnerabilities in myBloggie 2.1.6 and earlier allow remote attackers to execute arbitrary SQL…
CVE-2006-4042 — High (CVSS 7.5): Multiple SQL injection vulnerabilities in trackback.php in myWebland myBloggie 2.1.4 and earlier allow remote attackers…
CVE-2006-3905 — High (CVSS 7.5): SQL injection vulnerability in Webland MyBloggie 2.1.3 allows remote attackers to execute arbitrary SQL commands via…
CVE-2006-2859 — High (CVSS 7.5): PHP remote file inclusion vulnerability in MyBloggie 2.1.1 and earlier allows remote attackers to execute arbitrary PHP…
CVE-2005-4225 — High (CVSS 7.5): Multiple "potential" SQL injection vulnerabilities in myBloggie 2.1.3 beta might allow remote attackers to execute…

All CVEs affecting Mywebland Mybloggie →