CVE Intelligence
Skip to main content
MEDIUM

CVE-2023-6758

CVE-2023-6758 — Thecosy IceCMS API PlanetCommentList access control

A vulnerability was found in Thecosy IceCMS 2.0.1. It has been rated as critical. Affected by this issue is some unknown functionality of the file /adplanet/PlanetCommentList of the component API. The manipulation leads to improper access controls. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. VDB-247886 is the identifier assigned to this vulnerability.

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)

thecosy

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.1MEDIUM——cvelistV5

Weakness & attack patterns

  • CWE-284

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

  • T1027.009Obfuscated Files or Information: Embedded Payloads
  • T1546.004Event Triggered Execution: .bash_profile and .bashrc
  • T1546.016Event Triggered Execution: Installer Packages

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 /adplanet/PlanetCommentList.

References

3 on the record

Elsewhere on this site

  • thecosyevery CVE for this vendor
  • CWE-284other 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.