p PatchFirst

PatchFirst · Vulnérabilités récentes

Vulnérabilités de la pile PHP · Page n° 10

Vulnérabilités publiées pour PHP au cours des 30 derniers jours : 182. Présentes dans le catalogue KEV : 0.

Filtrer les vulnérabilités
PHP

Alertes précoces

Signalements récents de vulnérabilités issus des annonces des éditeurs et de l’actualité de la sécurité. Ces alertes ne modifient pas la note de sécurité.

  1. php

    Aucun correctif publié

    PHP : exécution de code à distance

    Selon OpenNet, PHP présente une vulnérabilité d’exécution de code à distance (CVE-2026-115560). Les versions exactes affectées ne sont pas précisées. Le message ne précise pas de version corrigée.

    Que faire maintenant : Vérifiez si une mise à jour de sécurité de PHP contenant le correctif est disponible et installez-la.

    CVE-2026-115560

Vulnérabilités : 7182

  1. CVE-2026-93682

    Moyenne · CVSS 5.8EPSS 0,37%Correctif disponible

    Out-of-bounds read in the HTTP stream wrapper when following a redirect with an empty Location header

    When the HTTP stream wrapper follows a redirect and the response carries a Location header with an empty value, the redirect code reads one byte past the end of the heap buffer holding the location. The value of that out-of-bounds byte decides which redirect target is built, so a malicious server controls whether the client is sent to the host root or to the current directory.

    • Mettez à jour vers 7.0.33-0ubuntu0.16.04.16+esm21
    • Mettez à jour vers 7.2.24-0ubuntu0.18.04.17+esm13
    • Mettez à jour vers 7.4.3-4ubuntu2.29+esm4
    • Mettez à jour vers 8.1.2-1ubuntu2.27
    • Mettez à jour vers 8.2.34
    • Mettez à jour vers 8.2.34-1~deb12u1
    • Mettez à jour vers 8.3.35
    • Mettez à jour vers 8.3.6-0ubuntu0.24.04.12
    • Mettez à jour vers 8.4.26
    • Mettez à jour vers 8.4.26-1
    • Mettez à jour vers 8.4.26-1~deb13u1
    • Mettez à jour vers 8.5.11
    • Mettez à jour vers 8.5.4-0ubuntu1.4
    • Mettez à jour vers 8.5.9-0ubuntu2
    Publication Mise à jour
  2. CVE-2026-92161

    Critique · CVSS 9.8EPSS 0,27%Correctif disponible

    FriendsOfFlarum OAuth: Unauthenticated account takeover via unverified email trust in Discord OAuth provider

    FriendsOfFlarum OAuth allows users to log in to Flarum with GitHub, Twitter, Facebook, and other providers. Prior to 1.7.4 and 2.0.0-beta.4, the Discord OAuth provider does not check the verified field returned for an OAuth email before passing the address to Flarum core as trusted through provideTrustedEmail(). When Discord sign-in is enabled, an unauthenticated attacker who knows the email address of a Flarum user can configure a Discord account with that unverified address and a verified phone number, then sign in to cause Flarum to match the trusted address, link the attacker-controlled Discord identity to the existing user, and authentic

    • Mettez à jour vers 1.7.4
    • Mettez à jour vers 2.0.0-beta.4
    Publication Mise à jour
  3. CVE-2026-57440

    Élevée · CVSS 7.5EPSS 0,26%Correctif disponible

    Mediawiki EmbedVideo Extension has stored XSS via malformed src url with $wgEmbedVideoRequireConsent disabled

    The EmbedVideo Extension is a MediaWiki extension which adds a parser function called #ev and various parser tags for embedding video clips from various video sharing services. Prior to 4.1.0, with $wgEmbedVideoRequireConsent disabled (not the default), the urls for videos are passed into an iframe src attribute without sanitization. When given a malformed url or id, the src attribute can be escaped via double quotes, allowing for html/javascript injection. Version 4.1.0 contains a patch.

    • Mettez à jour vers 4.1.0
    Publication Mise à jour
  4. CVE-2026-61823

    Élevée · CVSS 7.3EPSS 0,21%Correctif disponible

    code16 Sharp vulnerable to stored XSS via iframe srcdoc Attribute

    code16 Sharp is a Laravel-based framework for building content-management and administrative interfaces. Versions before 9.22.5 contain a stored cross-site scripting vulnerability in the rich-text editor because the HTML sanitizer permits the `srcdoc` attribute on iframe elements. Although markup inside `srcdoc` is HTML-encoded during sanitization, browsers decode attribute entities before interpreting the iframe document, allowing an authenticated user with permission to edit an Editor field to store executable JavaScript that runs when another user views the content. Successful exploitation can result in session hijacking, unauthorized acti

    • Mettez à jour vers 9.22.5
    Publication Mise à jour
  5. CVE-2026-61825

    Élevée · CVSS 8.7EPSS 0,22%Correctif disponible

    code16/sharp has a stored XSS via data-html-content Sanitizer Bypass

    code16 Sharp is a Laravel-based framework for building content-management and administrative interfaces. Versions before 9.22.5 contain a stored cross-site scripting vulnerability in `SharpEditorFormField`: attacker-controlled content bearing the `data-html-content` attribute can bypass HTML sanitization and preserve executable markup, which may execute when another user views the stored content. The vendor identifies version 9.22.5 as patched; applications that intentionally enable `SharpFormEditorField::RAW_HTML` must continue to sanitize editor content themselves. As a workaround, applications should sanitize all editor content before stor

    • Mettez à jour vers 9.22.5
    Publication Mise à jour
  6. CVE-2026-61816

    Élevée · CVSS 7.5EPSS 0,39%Correctif disponible

    zbateson/mail-mime-parser has uncontrolled resource consumption (CPU/memory DoS) parsing untrusted MIME

    zbateson/mail-mime-parser is a mail mime parser alternative to PHP's imap* functions and Pear libraries for reading messages in Internet Message Format RFC 822. Starting in version 2.0.0 and prior to version 3.0.6 and 4.0.2, an uncontrolled resource consumption / algorithmic complexity vulnerability (CWE-400) affects any application that parses untrusted email with this library. Three independent parsing paths are super-linear in cost, so a byte-size cap on the caller side does **not** bound the work done. A crafted message under 2 MB can consume seconds of CPU or hundreds of megabytes to multiple gigabytes of memory (leading to an out-of-me

    • Mettez à jour vers 3.0.6
    • Mettez à jour vers 4.0.2
    Publication Mise à jour
  7. CVE-2026-61815

    Élevée · CVSS 7.2EPSS 0,18%Correctif disponible

    zbateson/mail-mime-parser has CRLF header injection via attachment filename

    zbateson/mail-mime-parser is a mail mime parser alternative to PHP's imap* functions and Pear libraries for reading messages in Internet Message Format RFC 822. Prior to version 3.0.6 and 4.0.2, CRLF (carriage-return / line-feed) header injection (CWE-93) affecting any application that uses this library to build or forward MIME messages with an attacker-influenced attachment filename. Attachment filenames are interpolated into the `Content-Type` and `Content-Disposition` header values without stripping CR/LF, so a filename containing `\r\n` serializes as one or more additional, attacker-controlled header lines (for example a forged `Bcc:` tha

    • Mettez à jour vers 3.0.6
    • Mettez à jour vers 4.0.2
    Publication Mise à jour
  8. CVE-2026-62368

    Élevée · CVSS 8.1EPSS 0,35%Correctif disponible

    Snipe-IT: Stored XSS via Custom Field name in asset-list column headers

    Snipe-IT is an IT asset/license management system. Prior to 8.7.0, a user with the customfields.create permission can store markup in CustomField.name, and app/Presenters/AssetPresenter.php assigns that value as an unescaped bootstrap-table header title. When another user opens an asset-list page associated with the fieldset, the stored markup executes on page load in that user's Snipe-IT session. This can expose same-origin data and perform authenticated actions with the victim's privileges, including privilege escalation when a superuser views the affected list. This issue is fixed in version 8.7.0.

    • Mettez à jour vers 8.7.0
    Publication Mise à jour
  9. CVE-2026-63493

    Élevée · CVSS 8.6EPSS 0,27%Correctif disponible

    Snipe-IT: 2FA bypass via the API token flow

    Snipe-IT is an IT asset/license management system. Prior to 8.7.0, a password-authenticated session for an account with self.api permission can reach the personal-access-token API flow before completing the account's second-factor challenge because CheckForTwoFactor is enforced in the web middleware group but not the API middleware group. The advisory states that the resulting persistent API token can read and modify resources with the victim's permissions and, for an administrator, can reach the users/two_factor_reset endpoint. Resetting the administrator's enrolled second factor allows the password-holding attacker to enroll an attacker-con

    • Mettez à jour vers 8.7.0
    Publication Mise à jour
  10. CVE-2026-47132

    Moyenne · CVSS 5.4EPSS 0,25%Correctif disponible

    phpMyFAQ: SQL LIKE Wildcard Injection in Chat User Search Allows Authenticated User Enumeration

    phpMyFAQ is an open source FAQ web application. Prior to version 4.2.0-alpha, an authenticated SQL LIKE wildcard injection vulnerability in phpMyFAQ’s chat user search allows any logged-in user to bypass the intended display-name search filter and enumerate active users. The endpoint escapes SQL string syntax but does not escape `%` and `_`, which remain active `LIKE` wildcards. Version 4.2.0-alpha patches the issue.

    • Mettez à jour vers 4.2.0-alpha
    Publication Mise à jour
  11. CVE-2026-56738

    Élevée · CVSS 8.5EPSS 0,26%Code d’exploitation publicCorrectif disponible

    phpMyFAQ has SQL Injection in `StopWords::add()` — Unescaped Stop Word Insertion

    phpMyFAQ is an open source FAQ web application. The `StopWords::add()` method inversions prior to 4.1.6 builds a SQL `INSERT` statement using `sprintf()` and inserts the user-supplied stop word value directly into the query string without calling the application's database escaping function on it. A sibling method, `StopWords::update()`, which modifies an existing stop word, correctly escapes the same kind of input. The omission is isolated to the `add()` (insert) code path. An authenticated administrator who can reach the stop-word management feature can submit a crafted value as the "word" parameter that breaks out of the SQL string literal

    • Mettez à jour vers 4.1.6
    Publication Mise à jour
  12. CVE-2026-63498

    Élevée · CVSS 8.7EPSS 0,21%Correctif disponible

    Snipe-IT: Stored XSS via Inline XML Rendering in the Uploaded Files API

    Snipe-IT is an IT asset/license management system. Prior to 8.7.0, the uploaded-files API endpoint GET /api/v1/{object_type}/{id}/files/{file_id} allows an authenticated user with file-management access to upload XML and XSLT attachments and request them with the inline=true parameter. The app/Http/Controllers/Api/UploadedFilesController.php show() path does not apply the safe-inline allowlist used by the equivalent web controller, so the browser can process an attacker-controlled xml-stylesheet reference and execute JavaScript generated by the stylesheet in the Snipe-IT origin. A victim who is authorized to view the object must open the atta

    • Mettez à jour vers 8.7.0
    Publication Mise à jour
  13. CVE-2026-56737

    Élevée · CVSS 8.1EPSS 0,4%Correctif disponible

    phpMyFAQ's two-factor authentication login bypasses the password factor

    phpMyFAQ is an open source FAQ web application. Versions 3.2.0 through 4.1.5 contain an authentication bypass in its public two-factor authentication verification flow: an unauthenticated attacker can submit an account’s numeric user ID and a valid or brute-forced six-digit TOTP code without first authenticating with the account password, allowing takeover of any 2FA-enabled account, including administrator accounts. Version 4.1.6 is patched by binding TOTP verification to a session established after successful password authentication and limiting failed TOTP attempts. No official workaround is documented; affected installations should upgrad

    • Mettez à jour vers 4.1.6
    Publication Mise à jour
  14. CVE-2026-56736

    Élevée · CVSS 8.2EPSS 0,24%Correctif disponible

    phpMyFAQ has Stored XSS in Admin FAQ Editor via HTML Entity Bypass in Frontend FAQ Submission

    phpMyFAQ is an open source FAQ web application. A stored cross-site scripting (XSS) vulnerability in versions prior to 4.2.0-alpha allows any unauthenticated user (or low-privileged registered user) to inject arbitrary JavaScript that executes in an administrator's browser when they review or edit a user-submitted FAQ entry. This leads to admin account takeover via session theft. The vulnerability exists because `html_entity_decode()` converts HTML entities into executable HTML after `strip_tags()` has already passed them through, and the admin template renders the content with Twig's `|raw` filter without any output sanitization. Version 4.2

    • Mettez à jour vers 4.2.0-alpha
    Publication Mise à jour
  15. CVE-2026-76087

    Élevée · CVSS 8.2EPSS 0,31%Correctif disponible

    Formie: Unauthenticated users can overwrite incomplete submissions via submit action

    Formie is a Craft CMS plugin for creating forms. Prior to 2.2.23 and 3.1.31, Formie's anonymous formie/submissions/submit action in SubmissionsController::actionSubmit trusts a client-supplied submissionId when loading an incomplete submission without session binding, ownership validation, or a valid submissionEditToken. An unauthenticated attacker can enumerate sequential IDs and overwrite or hijack another user's in-progress multi-page or save-for-later submission, and the modified data can be persisted and forwarded through notifications or integrations when the submission is completed. This is an incomplete remediation of CVE-2026-47266 b

    • Mettez à jour vers 2.2.23
    • Mettez à jour vers 3.1.31
    Publication Mise à jour
  16. CVE-2026-76086

    Élevée · CVSS 8.5EPSS 0,29%Correctif disponible

    Formie: Integration form-settings action allows SSRF and exfiltration of stored integration credentials

    Formie is a Craft CMS plugin for creating forms. Prior to 2.2.23 and 3.1.31, Formie's formie/integrations/form-settings control panel action in IntegrationsController::actionFormSettings is reachable without the required form integration permissions and passes request-supplied settings to a configured integration. An authenticated attacker can replace outbound host properties such as apiUrl while the server uses stored API keys or OAuth tokens, causing non-blind server-side requests to an attacker-controlled or internal host and returning the remote response. This residual flaw remained because the permission gate added in version 3.1.28 excl

    • Mettez à jour vers 2.2.23
    • Mettez à jour vers 3.1.31
    Publication Mise à jour
  17. CVE-2026-76089

    Élevée · CVSS 7.7EPSS 0,24%Correctif disponible

    Formie: Missing authorization on sent notification resend modal exposes submission PII

    Formie is a Craft CMS plugin for creating forms. Prior to 2.2.23 and 3.1.31, Formie's formie/sent-notifications/get-resend-modal-content control panel action in SentNotificationsController::actionGetResendModalContent accepts a request-supplied notification ID without permission or object-level authorization checks. Any authenticated user able to invoke the action can enumerate notification IDs and read recipient headers and complete HTML email bodies containing submitted form data, even without the sent-notification viewing permission. This issue is fixed in versions 2.2.23 and 3.1.31.

    • Mettez à jour vers 2.2.23
    • Mettez à jour vers 3.1.31
    Publication Mise à jour
  18. CVE-2026-92692

    Moyenne · CVSS 6.9EPSS 0,33%Correctif disponible

    Sulu: JCR-SQL2 injection via `categories` query parameter (unauthenticated)

    Sulu is an open-source PHP content management system based on the Symfony framework. Prior to 2.6.25 and 3.0.8, the affected Sulu 2.6 and 3.0 release lines have a Smart Content QueryBuilder in src/Sulu/Component/Content/SmartContent/QueryBuilder.php that concatenates category identifiers from the public categories query parameter into a JCR-SQL2 WHERE clause without numeric validation. On a public page containing a category-filtered Smart Content block, an unauthenticated attacker can alter query conditions to infer or enumerate content-repository nodes, including unpublished content, or submit malformed and expensive query fragments that deg

    • Mettez à jour vers 2.6.25
    • Mettez à jour vers 3.0.8
    Publication Mise à jour
  19. CVE-2026-73858

    Moyenne · CVSS 5.3EPSS 0,43%Code d’exploitation publicCorrectif disponible

    Solspace Freeform: Limited Twig template injection via submitted field values

    Solspace Freeform plugin for Craft CMS 5.x is a super flexible form-building tool. From 5.0.0 through 5.10.13, submitted values from public Freeform forms can be evaluated by the isolated Twig renderer when rendered into HTML attributes. An unauthenticated attacker can place Twig expressions in submitted field values, including value attributes, and receive evaluated PHP, operating-system, or Craft filesystem-path constants in the form response. The isolated context was not shown to expose Craft globals, environment variables, credentials, arbitrary files, or code execution, so the confirmed impact is limited server and environment informatio

    • Mettez à jour vers 5.10.14
    Publication Mise à jour
  20. CVE-2026-88974

    Moyenne · CVSS 5.4EPSS 0,27%Aucun correctif publié

    WPGraphQL: Contributor can publish and modify posts without the required capabilities via updatePost

    WPGraphQL provides a GraphQL API for WordPress sites. Prior to 2.22.2, the updatePost mutation in src/Mutation/PostObjectUpdate.php checks only the collection-level edit_posts capability and the post author, but does not enforce the object-level edit_post capability or require publish_posts for public status transitions. An authenticated Contributor can therefore publish the Contributor's own draft without editorial approval or modify the Contributor's previously published post despite lacking edit_published_posts, while posts owned by other authors remain protected. This issue is fixed in version 2.22.2.

    Publication Mise à jour

Vérifiez votre serveur

Comparez votre pile et les versions installées aux bases de vulnérabilités actuelles.

Vérifiez votre serveur →