Report a Vulnerability
Submit, help fixing, get kudos.
Start a Bug Bounty
Run your bounty program for free.
534,224 coordinated disclosures
335,598 fixed vulnerabilities
788 bug bounties with 1,556 websites
16,024 researchers, 1104 honor badges

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


scielo.org Cross Site Scripting vulnerability
Open Bug Bounty ID: OBB-47041

Security Researcher unwritten0worm, found a security vulnerability affecting scielo.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.

Affected Website:scielo.org  
Open Bug Bounty Program:Create your bounty program now. It's open and free.
Vulnerable Application:Custom Code
Vulnerability Type:XSS (Cross Site Scripting) / CWE-79
CVSSv3 Score:6.1 [CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N]
Discovered and Reported by:unwritten0worm
Remediation Guide:OWASP XSS Prevention Cheat Sheet

Vulnerable URL:

Mirror: Click here to view the mirror

Coordinated Disclosure Timeline

Vulnerability Reported:26 July, 2014 00:22 GMT
Vulnerability Verified:26 July, 2014 00:24 GMT
Website Operator Notified:26 July, 2014 00:24 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]:
26 July, 2014 00:24 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.26 July, 2014 00:22 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.

scielo.org

Website Overview

Alexa Global Rank:121,067
SSL/TLS Server Test:B+    View Results
Web Server Security Test:F    View Results
Malware Test:Click here
Domain Health Report:Click here

Latest Submissions

OBB-ID Reported by Status Reported on
patched
24.02.2020
unpatched
22.08.2019
patched
10.03.2019
patched
05.02.2019
unpatched
30.04.2018
patched
28.04.2018
patched
23.03.2018
unpatched
09.12.2017
unpatched
02.11.2017
unpatched
26.06.2016
unpatched
29.08.2015
unpatched
13.04.2015
patched
07.04.2015
unpatched
26.07.2014

  Latest Patched

 03.06.2020 hopkinsmedicine.org
 03.06.2020 familydoctor.org
 03.06.2020 confirmtkt.com
 03.06.2020 team1x1.com
 03.06.2020 moneycontrol.com
 02.06.2020 portent.com
 02.06.2020 theses.fr
 02.06.2020 ebi.ac.uk

  Latest Blog Posts

04.04.2020 by Rando02355205
(Alibaba) message.alibaba.com [IDOR] - [Bug Bounty]
12.03.2020 by Rando02355205
(Paypal) www.paypal.com [CSP High Level] - [XSS Reflected] - [Bug Bounty] - [Write Up]
08.03.2020 by CybeReports
JDECO.net XSS Vulnerability| CybeReports
29.02.2020 by Rando02355205
(Google) groups.google.com - [Stored XSS] - [Bug Bounty] - [WriteUp] - [24/02/2020]
10.02.2020 by 0xrocky
Stored XSS on h2biz.net

  Recent Recommendations

    2 June, 2020
     haneynj:
Rajesh noted we had some vulnerabilities on one of our sites. When we reached out, he was helpful and shared his report. Thank you for reporting.
    2 June, 2020
     haraldbro:
Thank you for helping us identify an XSS. The description of the vulnerability was clear and allowed us to make a fix quickly.
    2 June, 2020
     leshaqe:
Thank you for making the web a better place. Professional and helpful contact.
    2 June, 2020
     PaulSaraber:
Thanks for reporting the vulnerability, and the detailed explanation of the mechanism and possible effects. This really contibuted to a quick resolution, the site developer exactly knew where to find and how t fix the issue.

All fixed, many thanks
    2 June, 2020
     Yaha_no:
Thank you very much for reporting a problem on our website and help with giving detailed description and explanations on how we could solve it.