Daily · Article 03 · 3 min read
- Security
PHP schedules critical fixes. Prepare for the 19 November release
18 November notice · release planned 19 November 23:00–23:30 JST/KST
Summary
PHP has announced security releases for all supported versions. Detailed conditions and fixed version numbers will accompany the release.
Key facts
This article records the advance notice as it stood at first publication.
The security team for PHP, the software that runs website programs on a server, posted an advance notice on 18 November. Releases are scheduled for 19 November, 14:00–14:30 UTC, which is 23:00–23:30 that day in Japan and Korea. They will address vulnerabilities affecting all supported PHP versions, with CRITICAL as the highest severity. The team says the CRITICAL issues require non-default configuration or uncommon setups. Detailed conditions and fixed version numbers will accompany the releases. PHP security-team notice
At this morning’s publication review, those fixed versions and detailed advisories were not yet available. Coverage of all supported versions does not establish that every site is exploitable in the same way. This advance notice does not establish your site’s exposure or whether exploitation has occurred.

1. A website update and the PHP running it
Imagine a small organization’s announcements site. When a visitor opens a page, PHP on the server executes the site’s program and produces the information needed for the page. Updating content or a plugin through the site’s dashboard changes that program. The new notice concerns PHP itself, which runs the program.
Ask the host which PHP branch and version actually serve web requests for your production site. Include the site address, so a version checked on a technician’s own computer is not mistaken for the version serving visitors.
The cat asks Q&A
- The researcher
Does pressing the site’s update button automatically apply the PHP fix too?
Pocket NotebookServer PHP may be managed separately, depending on the hosting arrangement. Identify who can change it, then obtain the live-site version and application time after release.
2. What is confirmed now and what comes later
Adding nine hours to the announced UTC window gives 23:00–23:30 in Japan and Korea. The 30 minutes describe a planned project release window, not your site’s downtime or a promise that its patching will finish then. The figure shows a general sequence: a schedule notice, later package availability, and the operator’s live-site check. Its clock symbolizes scheduling and does not show the release time.

The cat asks Q&A
- The researcher
Will the host have fixed our site when the clock reaches 23:00?
Pocket NotebookFirst establish that the PHP project actually released the fixes. The host’s availability time and your site’s application time require their own records.
3. Evidence that moves the work forward
Before release, identify the current branch, the person responsible for updates, and an available work period. Prepare backups, a restore procedure, and a way to test important functions. The attack mechanism and detailed settings are still unpublished, so this notice does not justify inventing a configuration change as its remedy.
| Stage and responsible party | Current state | Evidence to obtain next |
|---|---|---|
| Advance notice · PHP security team | Confirmed: supported versions affected, highest severity CRITICAL, detailed conditions unpublished | Original notice |
| Fixed release · PHP project | Planned: 19 November 23:00–23:30 JST/KST | Actual advisories, affected conditions, and fixed version numbers |
| Packages · host or deployment operator | Unverified for each provider | Package availability for your PHP branch and its availability time |
| Production application · site operator | Unverified for each site | Actual web PHP version, application/restart records, and important-function checks |
- Stage and responsible party
Advance notice · PHP security team
- Current state
- Confirmed: supported versions affected, highest severity CRITICAL, detailed conditions unpublished
- Evidence to obtain next
- Original notice
- Stage and responsible party
Fixed release · PHP project
- Current state
- Planned: 19 November 23:00–23:30 JST/KST
- Evidence to obtain next
- Actual advisories, affected conditions, and fixed version numbers
- Stage and responsible party
Packages · host or deployment operator
- Current state
- Unverified for each provider
- Evidence to obtain next
- Package availability for your PHP branch and its availability time
- Stage and responsible party
Production application · site operator
- Current state
- Unverified for each site
- Evidence to obtain next
- Actual web PHP version, application/restart records, and important-function checks
The cat asks Q&A
- The researcher
Can a site using defaults ignore this notice?
Pocket NotebookThe notice says only that the highest-severity issues require non-default configuration or uncommon setups. Compare the detailed advisory with the actual production configuration when it appears, and plan the fix for your branch.
To close
Assign responsibility before release, then compare versions and conditions
Obtain the production site’s PHP branch and update owner now. Tonight, check that actual advisories and fixed versions are available, rather than treating the scheduled time as completion, then follow through to records for each site.
Sources
- Original noticephp.net