maccmspro MacCMS up to 2026.1000.4056 Comment index Comment::saveData user_id dynamically-determined object attributes

Summaryinfo

A vulnerability marked as problematic has been reported in maccmspro MacCMS up to 2026.1000.4056. Affected by this vulnerability is the function index Comment::saveData of the component Comment. The manipulation of the argument user_id leads to dynamically-determined object attributes. This vulnerability is uniquely identified as CVE-2026-116216. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in maccmspro MacCMS up to 2026.1000.4056. It has been rated as problematic. This issue affects the function index Comment::saveData of the component Comment. The manipulation of the argument user_id with an unknown input leads to a dynamically-determined object attributes vulnerability. Using CWE to declare the problem leads to CWE-915. The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified. Impacted is integrity. The summary by CVE is:

MacCMS v10 through 2026.1000.4056 contains a mass assignment vulnerability in index/Comment::saveData() that allows unauthenticated attackers to set arbitrary mac_comment columns including user_id. Attackers can submit anonymous comments with a crafted user_id parameter to attribute them to any registered member, displaying that member's avatar and impersonating them.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-116216 since 10/25/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/26/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• maccmspro

Name

• MacCMS

Version

• 2026.1000.4056

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion