CVE-2008-0773: SQL injection vulnerability in Phil Taylor Comments (com_comments, aka Review Script) 0.5.8.5g and earlier com

Q: How do I fix CVE-2008-0773?

com comments: upgrade to newer than 0.5.8.5g; com comments: upgrade to newer than 0.5.8.5g; comments: upgrade to newer than 0.5.8.5g. Exact commands for each OS are on this page.

Q: Is CVE-2008-0773 being exploited?

CVE-2008-0773 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2008-0773 affect?

CVE-2008-0773 affects com comments, com comments, comments. Severity is high (CVSS 7.5). SQL injection vulnerability in Phil Taylor Comments (com_comments, aka Review Script) 0.5.8.5g and earlier component for Mambo allows remote attackers to execute arbitrary SQL commands via the id parameter.

Q: How urgent is CVE-2008-0773?

Priority 47/100. High severity; Public exploit reference

This month

HIGH 7.5UPGRADEUPGRADEUPGRADE

CVE-2008-0773 is a high-severity flaw (CVSS 7.5) affecting com comments, com comments, comments. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

SQL injection vulnerability in Phil Taylor Comments (com_comments, aka Review Script) 0.5.8.5g and earlier component for Mambo allows remote attackers to execute arbitrary SQL commands via the id parameter.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	1.1% (top 36%)
CISA exploited list	No
Weakness	CWE-89
Published	2008-02-14
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: joomla · mambo · phil taylor

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2008-02-14 00:00 UTCPublished CVE record published
2026-06-16 22:50 UTCUpdated Record last modified

joomla com comments UPGRADE

Affected: <= 0.5.8.5g

Fixed in: newer than 0.5.8.5g

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy com-comments || rpm -q com-comments || com-comments --version

2. UPGRADE to newer than 0.5.8.5g (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade com-comments

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade com-comments

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

mambo com comments UPGRADE

Affected: <= 0.5.8.5g

Fixed in: newer than 0.5.8.5g

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy com-comments || rpm -q com-comments || com-comments --version

2. UPGRADE to newer than 0.5.8.5g (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade com-comments

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade com-comments

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

phil taylor comments UPGRADE

Affected: <= 0.5.8.5g

Fixed in: newer than 0.5.8.5g

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy comments || rpm -q comments || comments --version

2. UPGRADE to newer than 0.5.8.5g (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade comments

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade comments

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

phil taylor review script UPGRADE

Affected: <= 0.5.8.5g

Fixed in: newer than 0.5.8.5g

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy review-script || rpm -q review-script || review-script --version

2. UPGRADE to newer than 0.5.8.5g (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade review-script

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade review-script

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: Mambo Component Comments 0.5.8.5g - SQL Injection

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2008-0773?

com comments: upgrade to newer than 0.5.8.5g; com comments: upgrade to newer than 0.5.8.5g; comments: upgrade to newer than 0.5.8.5g. Exact commands for each OS are on this page.

Is CVE-2008-0773 being exploited?

CVE-2008-0773 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2008-0773 affect?

CVE-2008-0773 affects com comments, com comments, comments. Severity is high (CVSS 7.5). SQL injection vulnerability in Phil Taylor Comments (com_comments, aka Review Script) 0.5.8.5g and earlier component for Mambo allows remote attackers to execute arbitrary SQL commands via the id parameter.

How urgent is CVE-2008-0773?

Priority 47/100. High severity; Public exploit reference

Software pages

Joomla vulnerabilities

References

← Back to latest CVEs