home.social

#phpaftershell — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #phpaftershell, aggregated by home.social.

  1. #PHP #Updates vom 19. Nov. 2026 fixen einige Schwachstellen. Zudem wurde PHP 8.6.0 freigegeben. Aber ... Sicherheitsforschern ist es gelungen, die #php2shell Fixes auszuhebeln - #phpAfterShell

    borncity.com/blog/2026/11/19/p

  2. ‼️ #phpAfterShell EXPLAINED: A critical PHP flaw (CVSS 9.2) could let attackers turn corrupted session files into remote code execution.

    The October #PHP2Shell patches didn't fix the underlying issue.

    How does the attack work, who's affected, and what's the fix?

    Learn here → thehackernews.com/2026/11/phpa

  3. CVE-2026-126714 #phpaftershell Can we like stop 😵‍💫
    Like it is good that those flaws are found but i am legit updating every day to patch a critical cve that affects my public facing services.
    secure.com/cve/cve-2026-126714

  4. Karen IT Security Response Center (@ksrc) Advisory

    Advisory ID: KSRC-2026-11193

    #Critical Security #Updates for #PHP
    Multiple Remote Code Execution Vulnerabilities Including #phpAfterShell (CVE-2026-126714) and #Session Serializer #Issues

    On 19 November 2026 the PHP project released security updates for all supported branches. The releases address approximately 18 vulnerabilities, of which seven are rated Critical (CVSS 9.2).

    Among the most significant issues is CVE-2026-126714 (referred to in the community as phpAfterShell), which can allow unauthenticated #remote code execution by manipulating partially overwritten session files and bypasses mitigations applied for the earlier #PHP2Shell #vulnerabilities. Several additional use-after-free and request-smuggling flaws capable of leading to remote code execution are also fixed. #vulnerability

    ksrc.karenit.net/blog/security

    #cve #cyberSecurity #staysafe #StayInformed #StayProtected

  5. 🚨 BREAKING: A NEW CRITICAL PHP VULNERABILITY COULD LET HACKERS EXECUTE CODE ON WEB SERVERS WITHOUT LOGGING IN.

    Dubbed phpAfterShell, CVE-2026-126714 carries a CVSS score of 9.2 and affects PHP's default file-based session handler.

    Security researchers at depthfirst discovered that interrupting a PHP session write can leave behind a corrupted session file containing attacker-controlled data. When PHP loads that session again, a suitable exploit chain can turn the corruption into remote code execution.

    The concerning part? Researchers demonstrated an attack path that begins while PHP is processing an unauthenticated file upload, before the application's PHP script even starts running. Exploitation still requires specific conditions, including a suitable deserialization chain.

    PHP 8.2, 8.3, 8.4 and 8.5 are affected. Security fixes are now available in versions 8.2.36, 8.3.37, 8.4.28 and 8.5.13.

    If you're running PHP applications with file-based sessions, check your versions and patch immediately.

    Full technical breakdown of phpAfterShell, how the attack works and the fixes ↓
    thecybersecguru.com/exploits/p

    #PHP #phpAfterShell #CyberSecurity #RCE #CVE

  6. phpAfterShell affects PHP’s default file-based session handler and can allow unauthenticated remote command execution.

    Applications using Redis or database-backed sessions are not affected.

    Fixed releases are PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13.

    PHP 8.0 and 8.1 are out of support and should be upgraded.

    A temporary workaround is to disable session.upload_progress.enabled.

    The issue has a CVSS v4.0 score of 9.2; there is n…

    en.hacks.gr/krisimo-provlima-s

    #PHP #phpAfterShell #CVSSv4 #PHPSessions

Share on Mastodon

Enter the server where you have an account.