Countly · ar2rsawseen · Jul 30, 2026 · Jul 29, 2026 · Jul 30, 2026 · Jul 30, 2026
diff --git a/SECURITY.md b/SECURITY.md
@@ -38,3 +38,5 @@ The following are out of scope. They may still be reported, and configuration is
 10. **Instances of a vulnerability class already under active remediation.** Findings that are additional instances of a vulnerability class we are already remediating — including work visible in an open or in-progress pull request, a public branch, or another not-yet-released fix — are considered part of that known, ongoing effort and are not separately eligible. Enumerating sibling occurrences of an issue from our published or in-progress remediation is not an independent discovery. Independently discovered issues remain welcome.
 
 11. **Cross-site scripting (XSS) without a working proof of concept.** XSS reports that do not demonstrate actual script execution in an authenticated dashboard session are out of scope. Pointing at a potential sink (for example a `v-html` binding or a DOM write) is not sufficient on its own, since the value reaching a sink may already be neutralized elsewhere in the request handling or rendering pipeline. XSS with a working end-to-end proof of concept — including DOM-based XSS that originates from the URL or other client-controlled input — is in scope and welcome.
+
+12. **Further instances of a root cause you have already reported.** Where a report is another instance of a root cause you previously reported to us — the same defective function, check, or pattern, reached through a different parameter, endpoint, or event — it is treated as part of that original report and is awarded once, under the original submission. We expect a report to cover the instances its own analysis reaches: having identified a root cause, enumerating the remaining places it applies is part of that finding rather than a new one. This applies whether or not we had finished remediating the first report. Independent discovery of the same class by a different researcher is assessed on its own merits, and genuinely distinct root causes are always separate reports.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -38,3 +38,5 @@ The following are out of scope. They may still be reported, and configuration is
		10. Instances of a vulnerability class already under active remediation. Findings that are additional instances of a vulnerability class we are already remediating — including work visible in an open or in-progress pull request, a public branch, or another not-yet-released fix — are considered part of that known, ongoing effort and are not separately eligible. Enumerating sibling occurrences of an issue from our published or in-progress remediation is not an independent discovery. Independently discovered issues remain welcome.

		11. Cross-site scripting (XSS) without a working proof of concept. XSS reports that do not demonstrate actual script execution in an authenticated dashboard session are out of scope. Pointing at a potential sink (for example a `v-html` binding or a DOM write) is not sufficient on its own, since the value reaching a sink may already be neutralized elsewhere in the request handling or rendering pipeline. XSS with a working end-to-end proof of concept — including DOM-based XSS that originates from the URL or other client-controlled input — is in scope and welcome.

		12. Further instances of a root cause you have already reported. Where a report is another instance of a root cause you previously reported to us — the same defective function, check, or pattern, reached through a different parameter, endpoint, or event — it is treated as part of that original report and is awarded once, under the original submission. We expect a report to cover the instances its own analysis reaches: having identified a root cause, enumerating the remaining places it applies is part of that finding rather than a new one. This applies whether or not we had finished remediating the first report. Independent discovery of the same class by a different researcher is assessed on its own merits, and genuinely distinct root causes are always separate reports.