What is the severity of CVE-2005-4801?

CVE-2005-4801 is considered a moderate severity vulnerability due to its potential for unauthorized actions via CSRF.

How do I fix CVE-2005-4801?

To fix CVE-2005-4801, you should upgrade to a version of YaPIG that is later than 0.95b, which addresses the CSRF vulnerabilities.

Which versions of YaPIG are affected by CVE-2005-4801?

CVE-2005-4801 affects YaPIG versions 0.95b and earlier, including versions 0.91 to 0.94u.

What types of attacks are possible with CVE-2005-4801?

CVE-2005-4801 allows attackers to execute unauthorized actions as a logged-in user through cross-site request forgery (CSRF) techniques.

Who is at risk from CVE-2005-4801?

Users of YaPIG, particularly those with administrative access, are at risk from CVE-2005-4801 due to the CSRF vulnerabilities.

Vulnerability/
CVE-2005-4801

high

7.5

CWE

NVD-CWE-Other 352

31/12/2005

15/5/2006

8/8/2024

CVE-2005-4801: CSRF

First published: Sat Dec 31 2005(Updated: )

Multiple cross-site request forgery (CSRF) vulnerabilities in Yet Another PHP Image Gallery (YaPIG) 0.95b and earlier allow remote attackers to perform unauthorized actions as a logged-in user, as demonstrated by tricking the administrator to access a web page that performs a mod_info action in modify_gallery.php.

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-4801?
CVE-2005-4801 is considered a moderate severity vulnerability due to its potential for unauthorized actions via CSRF.
How do I fix CVE-2005-4801?
To fix CVE-2005-4801, you should upgrade to a version of YaPIG that is later than 0.95b, which addresses the CSRF vulnerabilities.
Which versions of YaPIG are affected by CVE-2005-4801?
CVE-2005-4801 affects YaPIG versions 0.95b and earlier, including versions 0.91 to 0.94u.
What types of attacks are possible with CVE-2005-4801?
CVE-2005-4801 allows attackers to execute unauthorized actions as a logged-in user through cross-site request forgery (CSRF) techniques.
Who is at risk from CVE-2005-4801?
Users of YaPIG, particularly those with administrative access, are at risk from CVE-2005-4801 due to the CSRF vulnerabilities.

agent/type
agent/softwarecombine
agent/first-publish-date
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
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-4801?
CVE-2005-4801 is considered a moderate severity vulnerability due to its potential for unauthorized actions via CSRF.
How do I fix CVE-2005-4801?
To fix CVE-2005-4801, you should upgrade to a version of YaPIG that is later than 0.95b, which addresses the CSRF vulnerabilities.
Which versions of YaPIG are affected by CVE-2005-4801?
CVE-2005-4801 affects YaPIG versions 0.95b and earlier, including versions 0.91 to 0.94u.
What types of attacks are possible with CVE-2005-4801?
CVE-2005-4801 allows attackers to execute unauthorized actions as a logged-in user through cross-site request forgery (CSRF) techniques.
Who is at risk from CVE-2005-4801?
Users of YaPIG, particularly those with administrative access, are at risk from CVE-2005-4801 due to the CSRF vulnerabilities.