p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Schwachstellen im Stack PHP · Seite 27

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für PHP: 178. Davon im KEV-Katalog: 2.

Sicherheitslücken filtern
PHP

Frühwarnungen

Neue Schwachstellenmeldungen aus Herstellerankündigungen und Sicherheitsnachrichten. Diese Warnungen ändern die Sicherheitsbewertung nicht.

  1. php

    Keine Korrektur veröffentlicht

    PHP: Remote-Codeausführung

    Laut OpenNet wurde in PHP eine Sicherheitslücke gefunden: Remote-Codeausführung (CVE-2026-115560). Die betroffenen Versionen sind nicht genau angegeben. Im Bericht wird keine Version mit Fehlerbehebung genannt.

    Was jetzt zu tun ist: Prüfen Sie, ob ein Update für PHP mit der Fehlerbehebung verfügbar ist, und installieren Sie es.

    CVE-2026-115560

Sicherheitslücken: 7190

  1. CVE-2026-67339

    Mittel · CVSS 6.9EPSS 0,37%Korrektur verfügbar

    guzzlehttp/guzzle before 7.14.2 Proxy-Authorization Header Disclosure

    guzzlehttp/guzzle versions before 7.14.2 fail to properly isolate Proxy-Authorization headers from origin servers in cURL handlers. Attackers can capture proxy credentials through origin server access logs when requests are redirected, bypassed, or sent through SOCKS proxies that Guzzle misclassifies as direct connections.

    • Auf 7.14.2 aktualisieren
    • Auf 7.14.2-1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2026-54768

    Mittel · CVSS 6.9EPSS 0,45%Keine Korrektur veröffentlicht

    WPGraphQL has deprecated `user` field on SendPasswordResetEmailPayload that leaks user existence + profile (defeats explicit anti-enumeration design)

    WPGraphQL provides a GraphQL API for WordPress sites. From 2.0.0 until 2.15.1, the deprecated user field on SendPasswordResetEmailPayload lets an unauthenticated caller distinguish existing author-class accounts through the sendPasswordResetEmail mutation and obtain public profile fields. This issue is fixed in version 2.15.1.

    Veröffentlicht Aktualisiert
  3. CVE-2026-53599

    Hoch · CVSS 7.5EPSS 0,51%Korrektur verfügbar

    Redaxo has a Mediapool isAllowedExtension bypass via multi-segment filename that leads to authenticated RCE on Apache mod_php multi-extension handlers

    REDAXO is a PHP-based content management system. From 5.18.2 until 5.21.1, rex_mediapool::isAllowedExtension in redaxo/src/addons/mediapool/lib/mediapool.php lets an authenticated backend user with media[upload] permission upload a JPEG/PHP polyglot named shell.php.any.jpg, which web servers with multi-extension PHP handlers can execute as the web-server user. This issue is fixed in version 5.21.1.

    • Auf 5.21.1 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2026-55825

    Niedrig · CVSS 3.1EPSS 0,3%Korrektur verfügbar

    Contao: Possible path traversal in job download URIs

    Contao is an Open Source CMS. In versions 5.7.0 through 5.7.6, an authenticated backend user who can access one job can request an attachment identifier containing ../ segments and make the job attachment download endpoint read a file from another job directory inside var/job-attachments. The controller authorizes only the jobUuid route parameter. The later attachment lookup joins that authorized job UUID with the attacker-controlled identifier, then passes the combined path to the virtual filesystem. VirtualFilesystem::resolve() canonicalizes the whole path and only rejects paths that escape the filesystem mount, so authorized-job/../victim-

    • Auf 5.7.7 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2026-55824

    Niedrig · CVSS 2.6EPSS 0,24%Korrektur verfügbar

    Contao crawler leaks auth credentials to external hosts

    Contao is an Open Source CMS. In versions 4.13.40 through 5.3.46 and 5.7.0-RC1 through 5.7.6, the crawler leaks auth credentials to external hosts. Contao's crawler tries to prevent confidential HTTP client options from being sent to external domains by creating a scoped client: full options for root page origins, cleaned options for everything else. The cleaner removes Cookie and Authorization headers, but it removes the non-Symfony option names basic_auth and bearer_auth instead of Symfony HttpClient's real auth_basic and auth_bearer options. When contao.crawl.default_http_client_options contains Basic or Bearer authentication for a protect

    • Auf 5.3.47 aktualisieren
    • Auf 5.7.7 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2026-57232

    Niedrig · CVSS 3.1EPSS 0,29%Korrektur verfügbar

    Contao: Server-Side Request Forgery (SSRF) via Unvalidated RSS Feed URL in Feed Reader Module

    Contao is an Open Source CMS. From 5.3.35 through 5.3.47 and from 5.7.0-RC1 through 5.7.8, the Feed Reader front-end module passes configured RSS feed URLs from FeedReaderController::getResponse() to feedIo->read() without scheme or private-address validation, allowing a backend user with module-edit permissions to make the server request internal network services, loopback addresses, or cloud metadata endpoints. In core-bundle/src/Controller/FrontendModule/FeedReaderController.php, the getResponse() function iterates over the configured feed URLs and passes each one directly to the HTTP client (via $this->feedIo->read($url, new Feed())) with

    • Auf 5.3.48 aktualisieren
    • Auf 5.7.9 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2026-63223

    Kritisch · CVSS 9.8EPSS 0,8%Korrektur verfügbar

    CodeIgniter: Uploaded file extension validation bypass in is_image and mime_in rules

    CodeIgniter is a PHP full-stack web framework. Prior to 4.7.4, the is_image and mime_in upload validation rules do not independently enforce a safe client filename extension, allowing a remote attacker to upload executable content when an application preserves the client filename and stores uploads in a web-accessible script-enabled directory. Applications are impacted when they validate uploads using is_image or mime_in without an independent safe extension check (such as ext_in on patched versions), save uploaded files using the client-supplied filename, and place uploads in a web-accessible directory where PHP files can execute. This issue

    • Auf 4.7.4 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2026-63222

    Hoch · CVSS 7.5EPSS 0,64%Korrektur verfügbar

    CodeIgniter: Path traversal in UploadedFile::move() when using client-provided filenames

    CodeIgniter is a PHP full-stack web framework. Prior to 4.7.4, calling UploadedFile::move() without a second argument uses the client-provided filename without sanitization, allowing a remote attacker to use path traversal sequences to write uploaded content outside the intended directory when the application exposes an upload path. This issue is fixed in version 4.7.4.

    • Auf 4.7.4 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2026-63221

    Kritisch · CVSS 9.4EPSS 0,61%Korrektur verfügbar

    CodeIgniter: SQL injection is possible via Query Builder deleteBatch() when used with where() conditions

    CodeIgniter is a PHP full-stack web framework. From 4.3.0 through 4.7.3, Query Builder deleteBatch() substitutes bound values from where() conditions into generated SQL while ignoring their escape flags, allowing user-controlled condition values to be interpreted as SQL. This affects only the deleteBatch() code path. Regular delete() operations escape where() binds correctly. This issue is fixed in version 4.7.4.

    • Auf 4.7.4 aktualisieren
    Veröffentlicht Aktualisiert
  10. CVE-2026-63220

    Mittel · CVSS 4.8EPSS 0,17%Korrektur verfügbar

    CodeIgniter: Spoofable forwarded HTTPS headers in IncomingRequest::isSecure()

    CodeIgniter is a PHP full-stack web framework. In versions prior to 4.7.4, IncomingRequest::isSecure() trusted the X-Forwarded-Proto and Front-End-Https headers from any incoming request, allowing an attacker could spoof these headers and cause the application to incorrectly treat an HTTP request as secure. This may have impacted applications that rely on isSecure(), force_https(), forceGlobalSecureRequests, or similar logic to enforce HTTPS-only access or make security-sensitive decisions. Exploitability depends on deployment configuration. Applications are most exposed if the backend is reachable directly over HTTP, or if a reverse proxy/lo

    • Auf 4.7.4 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2026-68501

    Mittel · CVSS 6.5EPSS 0,6%Korrektur verfügbar

    Sylius Mollie Plugin: Unauthenticated IDOR leaks order token and customer PII

    Sylius Mollie Plugin provides Mollie payment integration for Sylius applications. Prior to 2.2.8, 3.2.4, and 3.3.1, Sylius Mollie Plugin's GET /{_locale}/thank-you PageRedirectController::thankYouAction and GET /{_locale}/get-code QrCodeAction::fetchQrCodeFromOrder endpoints look up sequential orderId values without ownership or session checks, exposing order tokenValue values that can be used with GET /{_locale}/register-after-checkout/{tokenValue} to view customer first name, last name, and email. This issue is fixed in 2.2.8, 3.2.4, and 3.3.1.

    • Auf 2.2.8 aktualisieren
    • Auf 3.2.4 aktualisieren
    • Auf 3.3.1 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2026-68500

    Hoch · CVSS 7.5EPSS 0,68%Korrektur verfügbar

    Sylius Mollie Plugin: Payment status forgery via the payment webhook

    Sylius Mollie Plugin provides Mollie payment integration for Sylius applications. Prior to 2.2.8, 3.2.4, and 3.3.1, Sylius Mollie Plugin's POST /{_locale}/update-payment payment webhook accepts attacker-controlled id and orderId parameters but does not verify that the Mollie payment belongs to the referenced Sylius order, allowing an unauthenticated attacker with any valid paid Mollie payment ID to mark a victim order as paid without transferring funds for that order. This issue is fixed in 2.2.8, 3.2.4, and 3.3.1.

    • Auf 2.2.8 aktualisieren
    • Auf 3.2.4 aktualisieren
    • Auf 3.3.1 aktualisieren
    Veröffentlicht Aktualisiert
  13. CVE-2026-7260

    Mittel · CVSS 5.4EPSS 0,11%Korrektur verfügbar

    Stack overflow in phar with circular symlinks

    Circular symbolic links in phar archives could lead to unbounded recursion, exhausting the C stack and crashing the PHP process, in PHP versions from 8.2.* before 8.2.33, from 8.3.* before 8.3.33, from 8.4.* before 8.4.24, and from 8.5.* before 8.5.9.

    • Auf 7.0.33-0ubuntu0.16.04.16+esm20 aktualisieren
    • Auf 8.1.2-1ubuntu2.26 aktualisieren
    • Auf 8.2.33 aktualisieren
    • Auf 8.2.33-1~deb12u1 aktualisieren
    • Auf 8.3.33 aktualisieren
    • Auf 8.3.6-0ubuntu0.24.04.11 aktualisieren
    • Auf 8.4.24 aktualisieren
    • Auf 8.4.24-1 aktualisieren
    • Auf 8.4.24-1~deb13u1 aktualisieren
    • Auf 8.5.4-0ubuntu1.3 aktualisieren
    • Auf 8.5.9 aktualisieren
    Veröffentlicht Aktualisiert
  14. CVE-2026-17544

    Hoch · CVSS 8.1EPSS 0,42%Korrektur verfügbar

    Out-of-bounds write in bccomp() via crafted operand and scale

    Attacker-provided inputs to bccomp() could lead to an out-of-bounds write with stack and heap corruption in PHP versions from 8.4.* before 8.4.24 and from 8.5.* before 8.5.9.

    • Auf 8.4.24 aktualisieren
    • Auf 8.4.24-1 aktualisieren
    • Auf 8.4.24-1~deb13u1 aktualisieren
    • Auf 8.5.4-0ubuntu1.3 aktualisieren
    • Auf 8.5.9 aktualisieren
    Veröffentlicht Aktualisiert
  15. CVE-2026-17543

    Hoch · CVSS 8.1EPSS 0,33%Korrektur verfügbar

    SQL injection in ext-pgsql via E'...' backslash breakout

    Improper escaping of backslashes in attacker-provided parameters would allow for trivial SQL injection in PHP versions from 8.2.* before 8.2.33, from 8.3.* before 8.3.33, from 8.4.* before 8.4.24, and from 8.5.* before 8.5.9.

    • Auf 7.0.33-0ubuntu0.16.04.16+esm20 aktualisieren
    • Auf 8.1.2-1ubuntu2.26 aktualisieren
    • Auf 8.2.33 aktualisieren
    • Auf 8.2.33-1~deb12u1 aktualisieren
    • Auf 8.3.33 aktualisieren
    • Auf 8.3.6-0ubuntu0.24.04.11 aktualisieren
    • Auf 8.4.24 aktualisieren
    • Auf 8.4.24-1 aktualisieren
    • Auf 8.4.24-1~deb13u1 aktualisieren
    • Auf 8.5.4-0ubuntu1.3 aktualisieren
    • Auf 8.5.9 aktualisieren
    Veröffentlicht Aktualisiert
  16. CVE-2026-59941

    Mittel · CVSS 6.3EPSS 0,64%Korrektur verfügbar

    Dompdf: Uncontrolled resource consumption based on declared BMP dimensions

    Dompdf is an HTML to PDF converter for PHP. Versions 3.15 and prior accept a BMP image and generates a PDF-compatible PNG based only on its declared header dimensions and never bounds width × height before the image is converted through GD. A 58-byte BMP whose header declares e.g. 6000×6000 is accepted and later drives imagecreatetruecolor($width, $height) (and PHP's native BMP decoder) to allocate the full pixel canvas. A payload can fit in a single HTTP request: the BMP can be inlined as a data:image/bmp;base64,… URI inside attacker-controlled HTML, so no upload, no remote fetch, and no chroot-reachable file is required. I measured a 169-by

    • Auf 3.1.6 aktualisieren
    Veröffentlicht Aktualisiert
  17. CVE-2026-59942

    Mittel · CVSS 6.3EPSS 0,9%Korrektur verfügbar

    Dompdf: Denial of Service (DoS) via Resource Exhaustion using Oversized Image Bitmaps

    Dompdf is an HTML to PDF converter for PHP. Versions 3.15 and prior are vulnerable to a Denial of Service (DoS) attack via resource exhaustion. An attacker can crash the PHP process by providing a specially crafted HTML document containing a single image with massive dimensions (e.g., 30,000x30,000 pixels). While Dompdf implements internal checks to validate image dimensions, these can be bypassed by using a high-entropy image (such as random noise) encoded in Base64 and wrapped in specific CSS containers. The vulnerability exists because the dimension validation happens early, but the resource allocation for calculating the object's bounding

    • Auf 3.1.6 aktualisieren
    Veröffentlicht Aktualisiert
  18. CVE-2026-59943

    Mittel · CVSS 6.3EPSS 0,42%Korrektur verfügbar

    Dompdf: Embedded SVG images can leak existence of files and directories within the filesystem

    Dompdf is an HTML to PDF converter for PHP. In versions 3.15 and prior, if a malicious actor can supply unrestricted content for rendering by Dompdf they can utilize the SVG rendering functionality to leak filesystem information when rendering PDF files using image references within a data-URI encoded SVG document. Using an <image> element inside a data-URI embedded SVG, an attacker can attempt to embed other files via the href or xlink:href attributes. When processing a file that does not exist (e.g. file:///DOESNOTEXIST), dompdf behaves differently than it does when accessing a file or directory that actually exists on the filesystem. This

    • Auf 3.1.6 aktualisieren
    Veröffentlicht Aktualisiert
  19. CVE-2026-56722

    Mittel · CVSS 6.3EPSS 0,45%Korrektur verfügbar

    Dompdf: Local file read due to improper file path validation in SVG images encoded as data-URI

    Dompdf is an HTML to PDF converter for PHP. In versions 3.15 and prior, aAn attacker who controls the HTML input can bypass this restriction by embedding a target file path inside an SVG image delivered through a  data:  URI, because dompdf processes the SVG twice and the second pass does not enforce the same protections as the first. When rendering, dompdf hands the SVG to the separate  php-svg-lib  library with external references forced on, and that library has no knowledge of the chroot directory, blocks only the  phar://  scheme, and ultimately reads the referenced file with no path or protocol validation. This lets an external, unauthen

    • Auf 3.1.6 aktualisieren
    Veröffentlicht Aktualisiert
  20. CVE-2026-55554

    Niedrig · CVSS 2.3EPSS 0,45%Korrektur verfügbar

    Dompdf: Chroot Validation Bypass

    Dompdf is an HTML to PDF converter for PHP. In versions 3.15 and prior, the validateLocalUri() method enforces chroot boundaries with a strpos() prefix check after normalizing paths with  realpath() . Because normalization strips the trailing directory separator from  $chrootPath , the check only verifies that  $chrootPath  is a string prefix of $realfile, so a chroot of  /var/www  also matches sibling directories like /var/www2 , /var/www-admin, or /var/www_backup. An attacker who controls part of the rendered HTML could exploit this to escape the chroot and read sensitive files outside the allowed directory. This issue has been fixed in ver

    • Auf 3.1.6 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →