How is XO affected by the recently-disclosed PHP vulnerability?
| ,.,..,.,..,.,.,.,..,.,.,,..,..,.,,..,.,,. | 10/21/26 | | Test | 10/21/26 | | ceo | 10/21/26 | | hex | 10/21/26 | | ceo | 10/21/26 | | hex | 10/21/26 | | ceo | 10/21/26 | | hex | 10/21/26 | | bloomington (retired) | 10/21/26 | | Historical American | 10/21/26 | | Test | 10/21/26 | | Nude Karlstack | 10/21/26 | | censorship | 10/21/26 | | .,.,.,.,,,,.,,.,.,.,...,,..,, | 10/22/26 | | censorship | 10/21/26 | | The Penis | 10/21/26 | | censorship | 10/21/26 | | The Penis | 10/21/26 | | Historical American | 10/21/26 | | The Penis | 10/21/26 | | Nude Karlstack | 10/26/26 |
Poast new message in this thread
Date: October 21st, 2026 5:18 PM
Author: ,.,..,.,..,.,.,.,..,.,.,,..,..,.,,..,.,,.
this sounds pretty bad - these guys claim that the exploit is basically Heartbleed Part II, but for PHP instead of OpenSSL:
https://www.wiz.io/blog/php2shell-php-rce
The Vulnerabilities
All of the disclosed vulnerabilities are memory-safety issues that stem from bugs in how PHP handles fatal errors while processing requests, particularly out-of-memory errors. These bugs can leave a corrupted internal PHP state behind after a request ends unexpectedly. A later request or worker can reuse that stale state, leading to memory disclosure or corruption.
Below you can find a table that demonstrates what type of impact was demonstrated by each of the bugs we reported to PHP. The applications listed below are targets we chose for the RCE demonstrations. They are representative targets - exploitation does not require one of these CMSs, as the vulnerable code is in PHP itself.
Tracking ID: CVE-2026-109618. Bug: Upload-progress unserializer use-after-free; Remote process-memory disclosure. What an attacker can achieve: Corrupt process memory and execute code; Unauthenticated disclosure of PHP worker memory. What we demonstrated: Pre-authentication RCE on WordPress, Drupal and Joomla; Application-agnostic remote memory disclosure
Tracking ID: CVE-2026-109619. Bug: Fatal-error backtrace use-after-free; OPcache type confusion. What an attacker can achieve: Corrupt process memory and execute code; Corrupt shared PHP state and execute code. What we demonstrated: Pre-authentication RCE on Drupal; Pre-authentication RCE on WordPress
While this blog covers only four instances of exploitable bugs (grouped under two CVEs) that follow this problematic pattern, there are other tracked, and likely untracked, variants of this issue in the PHP codebase. These variants have different requirements for exploitation and can lead to different types of impact.
Impact
We combined these vulnerabilities into a single exploit script, php2shell, and demonstrated that it could execute code remotely without authentication on deployments of WordPress (wordpress:latest), Drupal (drupal:latest), and Joomla (joomla:latest), using their latest container images at the time of testing.
These platforms illustrate the impact, but the vulnerabilities are in PHP itself. Exploitation does not depend on a flaw in the application’s code: even a simple “Hello World” application running on an affected PHP version can be vulnerable.
Separately, we demonstrated that attackers could read sensitive data from the PHP process’s memory, including passwords, tokens, and API keys, without needing to achieve remote code execution.
https://www.datocms-assets.com/75231/1792535785-image-5.png?fm=webp
https://www.datocms-assets.com/75231/1792537190-image-7.png?fm=webp
https://www.youtube.com/watch?v=H7JWNiQpaT8
basically, if you're running unpatched PHP, any random retard can take over your site and data.
(http://www.autoadmit.com/thread.php?thread_id=5914417&forum_id=2#50200507)
|
 |
Date: October 22nd, 2026 12:08 PM
Author: .,.,.,.,,,,.,,.,.,.,...,,..,,
Lol is this fr
(http://www.autoadmit.com/thread.php?thread_id=5914417&forum_id=2#50200664) |
|
|