Research collected from outside sources and what this site derives from them; every fact links to a saved copy of its source Research or story?

Stakeholders / Everyone with PHP in the path / The PHP project / The PHP security team

The PHP security team: its risk register

Received the reports, ran the embargo, published the advisories and the oss-security announcements.

Kind team · Assigned here 7 · In its register 7 · in the story as Jakub Zelenka, Alexandre Daubois, PHP security team

The register

Assigned here, or arriving through a part of this stakeholder. The part played is the one recorded for whoever holds the assignment.

Where its risks sit

Likelihood / impact1 Minor2 Moderate3 Significant4 Major5 Severe
5 Happening5 10 15 20 R02 R02-125
4 Likely4 8 12 R08-216 R02-320
3 Possible3 6 9 R02-212 R01-215 R01-4
2 Unlikely2 4 6 8 10
1 Rare1 2 3 4 5

Who it shares risks with

Organisations running PHP (3), The finders (3), Security lead and AppSec (2), Distributors and packagers (2), Managed PHP platforms (1), The fix authors (1), Platform engineers and developers (1), Calif (1), Edge, WAF and detection vendors (1), Critical infrastructure providers (1), Chainguard (1), The PHP Foundation (1)

The standards its register touches

NIST CSF 2.0 (3), ISO/IEC 27001 (3), NIST SSDF (3), ISO/IEC 29147 and 30111 (3), NIS2 (1), FIRST TLP 2.0 (1), Cyber Resilience Act (1), OWASP Top 10s (1)