What is the severity of CVE-2005-4800?

CVE-2005-4800 is categorized as a high severity vulnerability due to the potential for remote code execution.

How do I fix CVE-2005-4800?

To fix CVE-2005-4800, update to YaPIG version 0.96 or later, which addresses this vulnerability.

Who is affected by CVE-2005-4800?

CVE-2005-4800 affects versions of YaPIG up to and including 0.95b.

What type of vulnerability is CVE-2005-4800?

CVE-2005-4800 is a direct static code injection vulnerability.

What can attackers do with CVE-2005-4800?

Attackers can exploit CVE-2005-4800 to inject arbitrary PHP code into the application, potentially leading to full compromise.

Vulnerability/
CVE-2005-4800

critical

CWE

NVD-CWE-Other 352 94

31/12/2005

15/5/2006

8/8/2024

CVE-2005-4800: CSRF

First published: Sat Dec 31 2005(Updated: )

Direct static code injection vulnerability in Yet Another PHP Image Gallery (YaPIG) 0.95b and earlier allows remote authenticated administrators to inject arbitrary PHP code via the TestGallery parameter in a mod_info action to modify_gallery.php, which inserts the code into guid_info.php. NOTE: this issue is easier to exploit due to a separate CSRF vulnerability.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Yapig	=0.94u
Yapig	=0.93u
Yapig	=0.92b
Yapig	=0.95
Yapig	<=0.95b

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2005-4800?
CVE-2005-4800 is categorized as a high severity vulnerability due to the potential for remote code execution.
How do I fix CVE-2005-4800?
To fix CVE-2005-4800, update to YaPIG version 0.96 or later, which addresses this vulnerability.
Who is affected by CVE-2005-4800?
CVE-2005-4800 affects versions of YaPIG up to and including 0.95b.
What type of vulnerability is CVE-2005-4800?
CVE-2005-4800 is a direct static code injection vulnerability.
What can attackers do with CVE-2005-4800?
Attackers can exploit CVE-2005-4800 to inject arbitrary PHP code into the application, potentially leading to full compromise.

agent/first-publish-date
agent/type
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/references
agent/author
agent/weakness
agent/severity
agent/event
agent/description
agent/source
agent/tags
collector/nvd-historical
agent/software-canonical-lookup-request
collector/nvd-index
agent/softwarecombine
vendor/yapig
canonical/yapig
version/yapig/0.94u
version/yapig/0.93u
version/yapig/0.92b
version/yapig/0.95
version/yapig/0.95b

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-2005-4800?
CVE-2005-4800 is categorized as a high severity vulnerability due to the potential for remote code execution.
How do I fix CVE-2005-4800?
To fix CVE-2005-4800, update to YaPIG version 0.96 or later, which addresses this vulnerability.
Who is affected by CVE-2005-4800?
CVE-2005-4800 affects versions of YaPIG up to and including 0.95b.
What type of vulnerability is CVE-2005-4800?
CVE-2005-4800 is a direct static code injection vulnerability.
What can attackers do with CVE-2005-4800?
Attackers can exploit CVE-2005-4800 to inject arbitrary PHP code into the application, potentially leading to full compromise.