What is the severity of CVE-2004-1826?

CVE-2004-1826 is considered a critical severity vulnerability due to the potential for remote attackers to execute arbitrary SQL commands.

How do I fix CVE-2004-1826?

To fix CVE-2004-1826, upgrade Mambo Open Source to version 4.5 stable 1.0.4 or later.

Which versions of Mambo are affected by CVE-2004-1826?

CVE-2004-1826 affects Mambo Open Source versions 1.0.0 through 1.0.3 and beta versions.

Can CVE-2004-1826 lead to data compromise?

Yes, CVE-2004-1826 can lead to data compromise as it allows attackers to manipulate databases through SQL injection.

Is there a workaround for CVE-2004-1826?

There are no reliable workarounds for CVE-2004-1826; the best solution is to apply the software update.

Vulnerability/
CVE-2004-1826

high

7.5

CWE

NVD-CWE-Other 89

16/3/2004

10/5/2005

8/8/2024

CVE-2004-1826: SQL Injection

First published: Tue Mar 16 2004(Updated: )

SQL injection vulnerability in index.php in Mambo Open Source 4.5 stable 1.0.3 and earlier allows remote attackers to execute arbitrary SQL commands via the id parameter.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Mambo Mambo Open Source 4.5	=1.0.0
Mambo Mambo Open Source 4.5	=1.0.2
Mambo Mambo Open Source 4.5	=1.0.3beta
Mambo Mambo Open Source 4.5	=1.0.1
Mambo Mambo Open Source 4.5	=1.0.3

Remedy

http://secunia.com/advisories/11140

Remedy

http://www.osvdb.org/4307

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2004-1826?
CVE-2004-1826 is considered a critical severity vulnerability due to the potential for remote attackers to execute arbitrary SQL commands.
How do I fix CVE-2004-1826?
To fix CVE-2004-1826, upgrade Mambo Open Source to version 4.5 stable 1.0.4 or later.
Which versions of Mambo are affected by CVE-2004-1826?
CVE-2004-1826 affects Mambo Open Source versions 1.0.0 through 1.0.3 and beta versions.
Can CVE-2004-1826 lead to data compromise?
Yes, CVE-2004-1826 can lead to data compromise as it allows attackers to manipulate databases through SQL injection.
Is there a workaround for CVE-2004-1826?
There are no reliable workarounds for CVE-2004-1826; the best solution is to apply the software update.

collector/nvd-historical
collector/nvd-index
agent/type
agent/remedy
agent/first-publish-date
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/weakness
agent/references
agent/author
agent/last-modified-date
agent/event
agent/description
agent/tags
agent/source
vendor/mambo
canonical/mambo mambo open source 4.5
version/mambo mambo open source 4.5/1.0.0
version/mambo mambo open source 4.5/1.0.2
version/mambo mambo open source 4.5/1.0.3beta
version/mambo mambo open source 4.5/1.0.1
version/mambo mambo open source 4.5/1.0.3

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2004-1826?
CVE-2004-1826 is considered a critical severity vulnerability due to the potential for remote attackers to execute arbitrary SQL commands.
How do I fix CVE-2004-1826?
To fix CVE-2004-1826, upgrade Mambo Open Source to version 4.5 stable 1.0.4 or later.
Which versions of Mambo are affected by CVE-2004-1826?
CVE-2004-1826 affects Mambo Open Source versions 1.0.0 through 1.0.3 and beta versions.
Can CVE-2004-1826 lead to data compromise?
Yes, CVE-2004-1826 can lead to data compromise as it allows attackers to manipulate databases through SQL injection.
Is there a workaround for CVE-2004-1826?
There are no reliable workarounds for CVE-2004-1826; the best solution is to apply the software update.