CVE
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
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
- Exploited
- No known exploitation
- Fix
- Fixed in ead8da36a9452b961cc5361d6fd853ca68a58b08
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: ead8da36a9452b961cc5361d6fd853ca68a58b08.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Original 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.
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.
“TridotsTech go1cms master branch through commit 7f68d05”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: ead8da36a9452b961cc5361d6fd853ca68a58b08.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Timeline
- CVE published
- First seen by cve.now1 day
- Posted on X by cve.now
Affected versions
- TridotsTech go1cms
Version range not reported
Evidence 5
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130071
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: cve.now feed data
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: vulncheck.com
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: vulncheck.com
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: vulncheck.com