VulnerabilityPublished 9 Nov 2026

CVE-2026-124622: olivier-ls PHP-FTS · Time-of-check Time-of-use

Affects olivier-ls PHP-FTSSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.8 Medium · fixed in 1.1.4 : update olivier-ls PHP-FTS when convenient.

Data as of 9 Nov 2026, 13:33 UTC

CVSS 4.0 base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (VulDB)	CVSS 4.0	4.8
CNA (VulDB)	CVSS 3.1	5.3
CNA (VulDB)	CVSS 3.0	5.3
CNA (VulDB)	CVSS 2.0	4.3

Patch: Available – fixed in 1.1.4

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
olivier-lsPHP-FTS	Affected 1.1.0 – 1.1.3 4 affected builds	Fixed in–

CPE configurations (1)

cpe:2.3:a:olivier-ls:php-fts:*:*:*:*:*:*:*:*

AI-suggested

Upgrade olivier-ls PHP-FTS to version 1.1.4, which contains the official fix for this vulnerability. No additional mitigation is required if the upgrade is applied. The vendor notes this is a hardening measure for shared hosting scenarios and not a remotely exploitable vulnerability.

Description

CVE-2026-124622 is a time-of-check to time-of-use (TOCTOU) vulnerability in olivier-ls PHP-FTS versions 1.1.0 through 1.1.3. It affects the TrigramIndex::open function in Storage.php and requires local attack conditions where an attacker has write access to the index directory but is a different user than the application process. The vulnerability is considered a hardening issue rather than a remotely exploitable flaw. Upgrading to version 1.1.4 resolves the issue.

Impact

The vulnerability allows a local attacker with write access to the index directory to exploit a TOCTOU condition, potentially leading to code execution if the symlink target is a web-accessible PHP file. However, the attack requires specific conditions including local access and write permissions by a different user, limiting the risk primarily to shared hosting environments. The CVSS score of 4.8 reflects a medium severity with local attack vector and limited impact scope.

Summary

This vulnerability in olivier-ls PHP-FTS up to version 1.1.3 involves a TOCTOU race condition in the TrigramIndex::open function within Storage.php. An attacker with local write access to the index directory, distinct from the user running the application, can manipulate the index to exploit the timing window between checking and using a resource. The exploit scenario assumes a shared hosting environment and requires that the symlink target be a web-served PHP file to achieve code execution. The issue is fixed in version 1.1.4 by the patch identified as 0b2fae333d6b022da7ed4c43e2d41aa03f91dff3.

References

Community reviews

Loading reviews…