CVE-2026-2110VulnerabilityPublished 7 Feb 2026Updated 23 Feb 2026

CVE-2026-2110: Tasin1025 SwiftBuy · Improper Restriction of Excessive Authentication Attempts

Affects Tasin1025 SwiftBuySource CVE Database V5

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

6.3Medium

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

EPSS: 0.7% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Base metrics

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

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
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: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within 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.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-26.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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
Tasin1025SwiftBuy	Affected =0f5011372e8d1d7edfd642d57d721c9fadc54ec7	Fixed in–

AI-suggested

To mitigate CVE-2026-2110 effectively, organizations should implement multiple layers of defense beyond waiting for an official patch. First, deploy robust rate limiting on the /login.php endpoint to restrict the number of authentication attempts per IP address or user account within a defined time window. Second, implement account lockout policies that temporarily disable accounts after a threshold of failed login attempts, balancing security and usability. Third, enable multi-factor authentication (MFA) to add an additional verification layer that reduces the risk of unauthorized access even if credentials are compromised. Fourth, monitor authentication logs for unusual patterns indicative of brute-force or credential stuffing attacks and trigger alerts for investigation. Fifth, consider deploying web application firewalls (WAFs) with rules to detect and block automated login attempts. Sixth, educate users about strong, unique passwords and encourage the use of password managers. Finally, maintain an incident response plan to quickly address any detected compromise. Organizations should also engage with the vendor for updates and track community advisories for patches or workarounds.

Description

A security flaw has been discovered in Tasin1025 SwiftBuy up to 0f5011372e8d1d7edfd642d57d721c9fadc54ec7. Affected by this vulnerability is an unknown functionality of the file /login.php. Performing a manipulation results in improper restriction of excessive authentication attempts. Remote exploitation of the attack is possible. The attack's complexity is rated as high. The exploitation appears to be difficult. The exploit has been released to the public and may be used for attacks. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The primary impact of CVE-2026-2110 is an increased risk of unauthorized access to user accounts on SwiftBuy platforms due to the absence of effective controls limiting authentication attempts. Attackers can leverage this flaw to perform brute-force or credential stuffing attacks remotely, potentially compromising user credentials and gaining access to sensitive personal and financial information. This can lead to data breaches, financial fraud, and erosion of customer trust. While the vulnerability does not directly affect system integrity or availability, successful exploitation can result in unauthorized transactions or data exposure. Organizations relying on SwiftBuy for e-commerce operations may face reputational damage, regulatory penalties, and operational disruptions if attackers exploit this vulnerability. The lack of vendor response and patches exacerbates the risk, requiring organizations to adopt compensating controls promptly. The medium CVSS score reflects moderate severity, but the public availability of exploit code increases the urgency for mitigation.

References

Community reviews

Loading reviews…