What is the severity of CVE-2004-1571?

CVE-2004-1571 is categorized as a moderate severity vulnerability due to its potential to expose sensitive information.

How do I fix CVE-2004-1571?

To fix CVE-2004-1571, update AJ-Fork to a version that has addressed this vulnerability.

What types of information can be exposed by CVE-2004-1571?

CVE-2004-1571 can expose sensitive information through specific PHP files in the AJ-Fork installation.

Which version of AJ-Fork is affected by CVE-2004-1571?

CVE-2004-1571 affects AJ-Fork version 167.

Is CVE-2004-1571 a remote attack vulnerability?

Yes, CVE-2004-1571 allows remote attackers to exploit the vulnerability without needing local access.

Vulnerability/
CVE-2004-1571

medium

CWE

NVD-CWE-Other

31/12/2004

20/2/2005

8/8/2024

CVE-2004-1571

First published: Fri Dec 31 2004(Updated: )

AJ-Fork 167 allows remote attackers to gain sensitive information via a direct request to (1) auto-acronyms.php, (2) auto-archive.php, (3) ount-article-views.php, (4) kses.php, (5) custom-quick-tags.php, (6) disable-all-comments.php, (7) easy-date-format.php, (8) enable-disable-comments.php, (9) filter-by-author.php, (10) format-switcher.php, (11) long-to-short.php, (12) prospective-posting.php, or (13) sort-by-xfield.php, which displays the full path in an error message.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Aj-fork Aj-fork	=167

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2004-1571?
CVE-2004-1571 is categorized as a moderate severity vulnerability due to its potential to expose sensitive information.
How do I fix CVE-2004-1571?
To fix CVE-2004-1571, update AJ-Fork to a version that has addressed this vulnerability.
What types of information can be exposed by CVE-2004-1571?
CVE-2004-1571 can expose sensitive information through specific PHP files in the AJ-Fork installation.
Which version of AJ-Fork is affected by CVE-2004-1571?
CVE-2004-1571 affects AJ-Fork version 167.
Is CVE-2004-1571 a remote attack vulnerability?
Yes, CVE-2004-1571 allows remote attackers to exploit the vulnerability without needing local access.

collector/nvd-historical
collector/nvd-index
agent/type
agent/first-publish-date
agent/softwarecombine
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

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-1571?
CVE-2004-1571 is categorized as a moderate severity vulnerability due to its potential to expose sensitive information.
How do I fix CVE-2004-1571?
To fix CVE-2004-1571, update AJ-Fork to a version that has addressed this vulnerability.
What types of information can be exposed by CVE-2004-1571?
CVE-2004-1571 can expose sensitive information through specific PHP files in the AJ-Fork installation.
Which version of AJ-Fork is affected by CVE-2004-1571?
CVE-2004-1571 affects AJ-Fork version 167.
Is CVE-2004-1571 a remote attack vulnerability?
Yes, CVE-2004-1571 allows remote attackers to exploit the vulnerability without needing local access.