Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[GHSA-4xvf-3477-vq63] SQL injection vulnerability found in Piwigo v.13.5.0 and... #5126

Closed

Conversation

rodnt
Copy link

@rodnt rodnt commented Dec 24, 2024

Updates

  • Affected products
  • Source code location
  • Summary

Comments
Hello GitHub Team,

My name is Rodolfo Tavares, and I am the author of the CVE related to the GitHub Advisory GHSA-4xvf-3477-vq63. I was also responsible for creating the proof-of-concept and for the initial discovery of the vulnerability described in this advisory.

I would like to know how I can ensure that this CVE is associated with my GitHub profile and displayed in the contribution section of my profile.

If you require additional information or evidence, I am happy to provide further details as needed.

Thank you in advance for your assistance!

Best regards,
Rodolfo Tavares - rodnt.github.io

@github-actions github-actions bot changed the base branch from main to rodnt/advisory-improvement-5126 December 24, 2024 12:12
@shelbyc
Copy link
Contributor

shelbyc commented Dec 26, 2024

👋 Hello @rodnt, Piwigo is not in one of the GitHub Advisory Database's supported ecosystems, which means that we can't make changes (such as adding credits) to the advisory. Making changes to the advisory would require Piwigo to be in a supported ecosystem and be able to send alerts. Thank you for your interest in the GitHub Advisory Database and have a nice day!

@shelbyc shelbyc closed this Dec 26, 2024
@github-actions github-actions bot deleted the rodnt-GHSA-4xvf-3477-vq63 branch December 26, 2024 15:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants