Released finding
A PHP emergency, from an early attack trace to published fixes
An attributed early attack trace, defensive discovery and published fixes, with deployment and attack outcomes unmeasured.
Follow the connections
These are explicit references between records. The link itself does not establish support or intellectual influence.
Referenced by this record
- PHP flaws in CISA's exploited list study
- What did PHP's own 23 October notice say about a related issue in the fixed releases? study
- An emergency patch had several public kinds of protection study
- Five derived PHP image tags already declared fixed versions study
- Drupal's published layers extend the fixed PHP base layers study
- The first public attack trace predates the PHP disclosure, but says little about AI use by attackers study
- Where does a software update go? investigation
Records that refer back here
Reviews and checking history · 12
- R-0029: PHP emergency account, evidence review
- R-0030: PHP emergency account, reader-and-inference review
- R-0031: PHP emergency reader-and-inference review
- R-0032: Evidence review of the PHP account's later evidence (version 1.1)
- R-0033: Reader-and-inference review of the PHP account, version 1.1
- R-0034: Recheck of what the two reviews' resolutions wrote (PHP account, version 1.1)
- R-0035: Evidence review of the PHP account's CISA later evidence (version 1.2)
- R-0036: Reader-and-inference review of the PHP account, version 1.2
- R-0037: Recheck of the resolutions to R-0035 and R-0036 (PHP account, version 1.2)
- R-0043: evidence review of the PHP account's version 1.3 (later evidence of 30 October)
- R-0044, reader-and-inference review of the PHP account, version 1.3
- R-0045, recheck of the PHP account's version 1.3 resolutions
Navigation summary checked against the retained record. A record being written does not by itself mean that its study or investigation has ended.