Cyber & AI intelligence
Briefs indexed3792
Issues37
Published Mondays07:30 CT
⚡ Active KEV CVE-2026-130071 2026-11-17

CVE-2026-130071: Unauthenticated Arbitrary Document Modification in TridotsTech go1cms

"A critical missing-authentication flaw in go1cms's guest-whitelisted `update_doc` method lets unauthenticated attackers modify any document, including User records."

A critical missing-authentication flaw in go1cms's guest-whitelisted update_doc method lets unauthenticated attackers modify any document, including User records.

What Is It

CVE-2026-130071 is a missing authentication vulnerability (CWE-306) in TridotsTech go1cms. The update_doc method is whitelisted for guest access, so it can be called without logging in. An attacker supplies a doctype, a document name and arbitrary fields. The method then saves those fields with ignore_permissions=True, which bypasses the application's permission checks.

VulnCheck ([email protected]) reported the issue. NVD published the record on 2026-11-16 with a status of "Received." The vulnerable code is in web_page_builder.py in the go1cms repository.

Why It Matters

VulnCheck rates the flaw CVSS 3.1 9.8 (Critical) with vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The CVSS 4.0 score is 9.3 (Critical). Exploitation works over the network, needs low complexity, and requires no privileges and no user interaction.

Any document can be modified, so the impact is broad. According to the record, attackers can:

Confidentiality, integrity and availability impacts are all rated High.

None of the sources cited in this brief reports active exploitation or references a CISA Known Exploited Vulnerabilities entry for this CVE.

What's Vulnerable

In the affected-versions data, every git revision before commit ead8da36a9452b961cc5361d6fd853ca68a58b08 is affected. The record lists no CPEs.

Patch Status

A fix is in commit ead8da36a9452b961cc5361d6fd853ca68a58b08 on the version-3 branch. Anyone running go1cms should update to a revision that includes this commit.

The record describes the master branch as vulnerable "through commit 7f68d05" and names no master-branch fix. Deployments built from master should check whether the fix is present.

The cited sources give no federal remediation due date. Because the attack path is unauthenticated and the severity is critical, patching should still be a priority.

Sources