CVE Intelligence
Skip to main content
MEDIUM

CVE-2023-6756

CVE-2023-6756 — Thecosy IceCMS Captcha login excessive authentication

A vulnerability was found in Thecosy IceCMS 2.0.1. It has been classified as problematic. Affected is an unknown function of the file /login of the component Captcha Handler. The manipulation leads to improper restriction of excessive authentication attempts. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-247884.

Published Updated Sources: cvelistV5, VulDB

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

1%

chance of exploitation in 30 days

Affects

thecosy

icecms

CVSS base

5.3

MEDIUM

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

Products (1)

icecms

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
5.3CVSS 3.1MEDIUMcvelistV5

Weakness & attack patterns

  • CWE-307

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1110.001Brute Force: Password Guessing
  • T1078Valid Accounts
  • T1110.003Brute Force: Password Spraying

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Search application, proxy, and WAF logs for requests touching /login.

References

3 on the record

Elsewhere on this site

  • thecosyevery CVE for this vendor
  • CWE-307other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.