Description

A vulnerability has been found in olivier-ls PHP-FTS up to 1.1.3. This affects the function SearchEngine::matchesSingleFilter of the file src/SearchEngine.php of the component Filter Matching. The manipulation leads to incorrect comparison. Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used. Upgrading to version 1.1.4 is able to mitigate this issue. The identifier of the patch is 0b2fae333d6b022da7ed4c43e2d41aa03f91dff3. It is suggested to upgrade the affected component. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "4.3",
  "pubDate": "2026-09-20T02:16:52.973Z",
  "pubdate": "2026-09-20T02:16:52.973Z",
  "executiveSummary": "A critical incorrect comparison vulnerability has been identified in the olivier-ls PHP-FTS component, affecting all versions up to and including 1.1.3.\nThe vulnerability resides within the SearchEngine::matchesSingleFilter function in src/SearchEngine.php, stemming from flawed logic during the filter evaluation process.\nThis vulnerability allows for remote exploitation, enabling an attacker to bypass intended search constraints or manipulate filter logic.\nThe risk implication is significant as the flaw permits unauthorized data matching or potential information disclosure through manipulated search queries.\nThe attack is remotely executable without requiring authentication, making it highly accessible to external threat actors.\nPublic exploit code is currently available, elevating the risk of active exploitation in unpatched environments.\nThe vendor has responded effectively, providing a remediation path in version 1.1.4.",
  "technicalDetails": "The vulnerability is an incorrect comparison flaw located in the SearchEngine::matchesSingleFilter function within src/SearchEngine.php of the olivier-ls PHP-FTS component. This component is responsible for handling search filter logic and matching criteria against data sets.\nThe root cause is a logical error in the comparison operation used to evaluate filter conditions. In PHP, incorrect use of equality operators or loose type comparisons during filter validation can lead to unintended matches, where inputs that should fail a validation check are erroneously evaluated as true.\nThe attack flow begins when an attacker crafts a malicious search request or input that interacts with the filtering mechanism. Because the matchesSingleFilter function performs flawed comparison logic, the attacker can supply specially crafted filter parameters that satisfy the incorrect comparison condition, despite not meeting the legitimate security or functional requirements defined by the application.\nSince the vulnerability is triggered via the search/filtering interface, it is accessible via remote network requests. Exploitation does not require prior authentication or elevated privileges, as the comparison logic flaw is inherent in the processing of search parameters passed to the function.\nUpon successful exploitation, the payload behavior manifests as a bypass of the filtering engine. The attacker can force the SearchEngine to return results that should have been excluded by the filter, or potentially leverage the logic flaw to perform unauthorized data extraction depending on the structure of the underlying data being queried.\nThe post-exploitation impact includes the potential for information disclosure, as the attacker can manipulate the search results to view data they are not authorized to access or to retrieve data that violates the intended scope of the search operation. Given the public disclosure of an exploit, the vulnerability poses a high risk to availability and data confidentiality of the affected PHP-FTS implementation.\nThe issue is remediated in version 1.1.4, which includes patch 0b2fae333d6b022da7ed4c43e2d41aa03f91dff3. This patch corrects the comparison logic within src/SearchEngine.php to ensure that filters are evaluated strictly and accurately, preventing the bypass condition identified in earlier versions."
}