Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2007-0374: SQL injection vulnerability in (1) Joomla! 1.0.11 and 1.5 Beta, and (2) Mambo 4.6.1, allows remote attackers t

49
This month
HIGH 7.5DOWNGRADEDOWNGRADE

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

SQL injection vulnerability in (1) Joomla! 1.0.11 and 1.5 Beta, and (2) Mambo 4.6.1, allows remote attackers to execute arbitrary SQL commands via the id parameter when cancelling content editing.

Why this priority

  • High severity
  • Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score7.5 (High)
EPSS exploit chance1.3% (top 30%)
CISA exploited listNo
Published2007-01-19
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: joomla · mambo

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

joomla joomla DOWNGRADE
Affected: 1.0.11 · 1.5.0_beta
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.0.11
1. Check installed version
apt-cache policy joomla || rpm -q joomla || joomla --version
2. No fixed release: DOWNGRADE to a release before 1.0.11 (Debian / Ubuntu)
apt-cache madison joomla sudo apt install joomla=<VERSION_BEFORE_1.0.11> sudo apt-mark hold joomla
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list joomla sudo dnf downgrade joomla-<VERSION_BEFORE_1.0.11> sudo dnf versionlock add joomla
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
mambo mambo DOWNGRADE
Affected: 4.6.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 4.6.1
1. Check installed version
apt-cache policy mambo || rpm -q mambo || mambo --version
2. No fixed release: DOWNGRADE to a release before 4.6.1 (Debian / Ubuntu)
apt-cache madison mambo sudo apt install mambo=<VERSION_BEFORE_4.6.1> sudo apt-mark hold mambo
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list mambo sudo dnf downgrade mambo-<VERSION_BEFORE_4.6.1> sudo dnf versionlock add mambo
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
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-2007-0374?

joomla: downgrade or apply the listed mitigation; mambo: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2007-0374 being exploited?

CVE-2007-0374 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-2007-0374 affect?

CVE-2007-0374 affects joomla, mambo. Severity is high (CVSS 7.5). SQL injection vulnerability in (1) Joomla! 1.0.11 and 1.5 Beta, and (2) Mambo 4.6.1, allows remote attackers to execute arbitrary SQL commands via the id parameter when cancelling content editing.

How urgent is CVE-2007-0374?

Priority 49/100. High severity; Public exploit reference

Software pages

Joomla vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.