What is the severity of CVE-2004-1573?

CVE-2004-1573 is considered a high severity vulnerability due to the potential for arbitrary code execution.

How do I fix CVE-2004-1573?

To fix CVE-2004-1573, ensure that the permissions for users.db.php are set to a more secure setting, such as 644, rather than 777.

What systems are affected by CVE-2004-1573?

CVE-2004-1573 affects AJ-Fork 167 and multiple versions of CuteNews, including 1.3.6, 1.3.2, 0.88, 1.3, and 1.3.1.

What is the impact of exploiting CVE-2004-1573?

Exploiting CVE-2004-1573 allows local users to execute arbitrary PHP code, potentially gaining administrative privileges.

Can CVE-2004-1573 be mitigated?

Mitigation for CVE-2004-1573 includes setting proper file permissions and regularly auditing file access configurations.

Vulnerability/
CVE-2004-1573

high

7.2

CWE

NVD-CWE-Other

31/12/2004

20/2/2005

8/8/2024

CVE-2004-1573

First published: Fri Dec 31 2004(Updated: )

The documentation for AJ-Fork 167 implies that users should set permissions for users.db.php to 777, which allows local users to execute arbitrary PHP code and gain privileges as the administrator.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Aj-fork Aj-fork	=167
CutePHP CuteNews	=1.3.6
CutePHP CuteNews	=1.3.2
CutePHP CuteNews	=0.88
CutePHP CuteNews	=1.3
CutePHP CuteNews	=1.3.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2004-1573?
CVE-2004-1573 is considered a high severity vulnerability due to the potential for arbitrary code execution.
How do I fix CVE-2004-1573?
To fix CVE-2004-1573, ensure that the permissions for users.db.php are set to a more secure setting, such as 644, rather than 777.
What systems are affected by CVE-2004-1573?
CVE-2004-1573 affects AJ-Fork 167 and multiple versions of CuteNews, including 1.3.6, 1.3.2, 0.88, 1.3, and 1.3.1.
What is the impact of exploiting CVE-2004-1573?
Exploiting CVE-2004-1573 allows local users to execute arbitrary PHP code, potentially gaining administrative privileges.
Can CVE-2004-1573 be mitigated?
Mitigation for CVE-2004-1573 includes setting proper file permissions and regularly auditing file access configurations.

collector/nvd-historical
collector/nvd-index
agent/type
agent/softwarecombine
agent/first-publish-date
collector/mitre-cve
source/MITRE
agent/references
agent/author
agent/weakness
agent/severity
agent/last-modified-date
agent/tags
agent/description
agent/event
agent/source
vendor/aj-fork
canonical/aj-fork aj-fork
version/aj-fork aj-fork/167
vendor/cutephp
canonical/cutephp cutenews
version/cutephp cutenews/1.3.6
version/cutephp cutenews/1.3.2
version/cutephp cutenews/0.88
version/cutephp cutenews/1.3
version/cutephp cutenews/1.3.1

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-1573?
CVE-2004-1573 is considered a high severity vulnerability due to the potential for arbitrary code execution.
How do I fix CVE-2004-1573?
To fix CVE-2004-1573, ensure that the permissions for users.db.php are set to a more secure setting, such as 644, rather than 777.
What systems are affected by CVE-2004-1573?
CVE-2004-1573 affects AJ-Fork 167 and multiple versions of CuteNews, including 1.3.6, 1.3.2, 0.88, 1.3, and 1.3.1.
What is the impact of exploiting CVE-2004-1573?
Exploiting CVE-2004-1573 allows local users to execute arbitrary PHP code, potentially gaining administrative privileges.
Can CVE-2004-1573 be mitigated?
Mitigation for CVE-2004-1573 includes setting proper file permissions and regularly auditing file access configurations.