Are you sure you want to delete the vulnerability? Yes No

This feature enables you to send additional notifications to the website owners or admins after the vulnerability is submitted. The total number of additional notification is limited to 10, and to 1 in 24 hours. Notify specific security contact:

To my best knowledge this email belongs to the website owner/admin



archive.org Cross Site Scripting vulnerability | OBB-154767

Security Researcher 1995eaton Helped patch 716 vulnerabilities

Received 5 Coordinated Disclosure badges

Received 13 recommendations , a holder of 5 badges for responsible and coordinated disclosure, found a security vulnerability affecting archive.org website and its users.

Following coordinated and responsible vulnerability disclosure guidelines of the ISO 29147 standard, Open Bug Bounty has:

a. verified the vulnerability and confirmed its existence;

b. notified the website operator about its existence.

Vulnerable URL:

Mirror: Click here to view the mirror

Coordinated Disclosure Timeline

Vulnerability Reported: 20 May, 2016 07:03 GMT Vulnerability Verified: 20 May, 2016 07:06 GMT Website Operator Notified: 20 May, 2016 07:06 GMT

a. Using publicly available security contacts b. Using Open Bug Bounty notification framework c. Using security contacts provided by the researcher Public Report Published

[without any technical details]: 20 May, 2016 07:06 GMT

Vulnerability Fixed: 27 July, 2017 09:14 GMT

Public Disclosure: A security researcher can delete the report before public disclosure, afterwards the report cannot be deleted or modified anymore. The researcher can also postpone public disclosure date as long as reasonably required to remediate the vulnerability. 20 May, 2016 07:03 GMT

For Website Operators and Owners

Please contact the researcher directly to get the vulnerability details. The researcher may also help you fix the vulnerability and advice on how to prevent similar issues:







For remediation best practices, please also refer to OWASP remediation guidelines. More information about coordinate and responsible disclosure on Open Bug Bounty is available here.

DISCLAIMER: As a non-profit project, Open Bug Bounty never acts as an intermediary between website owners and security researchers. Our role is strictly limited to independent verification of the reports and proper notification of website owners by all available means.

archive.org

Website Overview

Latest Submissions