On this page (7 sections)

CVE-2026-130071 is a critical missing-authentication flaw in TridotsTech go1cms. According to the NVD record, a method named update_doc is whitelisted for guest (not logged in) users, so an unauthenticated attacker can modify any document the application stores, including User records.

If you run go1cms, or host or maintain sites for clients who do, you should check which commit your installation is on and update. The record was published on 2026-11-16, and at the time of writing only the NVD record and the references attached to it describe the issue.

What happened

The NVD entry describes a guest-whitelisted update_doc method that does not require authentication. An attacker supplies a doctype, a document name and arbitrary fields, and the application saves them with ignore_permissions=True. That flag tells the framework to skip its normal permission checks, so the request is accepted even though the caller has no account.

The record says this can be used to alter User records to escalate privileges, take over accounts or tamper with business data. The VulnCheck advisory is referenced as the write-up. This story currently rests on a single publisher, so details beyond the NVD description should be treated as unconfirmed until more sources appear.

Why this class of bug is serious

Missing authentication on a critical function (CWE-306) means the application never asks who is calling. Normally a content system checks that the user is logged in and allowed to edit a given record. Here the endpoint is open to guests and the permission check is switched off, so the only limit is what the attacker chooses to write.

Because the target is any document type, the impact is not limited to one page or setting. Editing a User record could change a role or credentials, which is how the record describes privilege escalation and account takeover. Editing business documents could silently change content or data your site relies on.

Who is affected

  • Sites running the go1cms master branch at or before commit 7f68d05.
  • Sites running the version-3 branch at a commit before ead8da3.
  • Agencies and hosts that deployed go1cms for clients and may not track which commit is live.

The research does not list a packaged release or version number, so exposure is determined by the commit your deployment was built from. The master branch is described as affected through commit 7f68d05, and the record does not name a fixed master commit, so check the project repository for newer commits.

How to check your exposure

If your go1cms code was installed from a git checkout, this read-only command prints the commit currently deployed. Run it in the application directory and compare the result with the commits named above.

Show the deployed commit (run in the go1cms app directory)Shell
git rev-parse --short HEAD

To see whether the fix commit is already part of your checkout, run the following. It prints a confirmation only if commit ead8da3 is in your history. If your remote has not been fetched recently, run a fetch first.

Check whether the version-3 fix commit is in your historyShell
git merge-base --is-ancestor ead8da3 HEAD && echo "fix commit present" || echo "fix commit NOT present"
This check applies to the version-3 branch. For master, the record only says commits through 7f68d05 are affected, so confirm with the maintainers or the repository which later commit addresses it.

What to do now

  1. Identify every go1cms installation you run or manage and record the branch and commit of each.
  2. For the version-3 branch, update to a commit at or after ead8da3 using the fix commit.
  3. For master, move to a commit later than 7f68d05 if one exists in the repository, and ask the maintainers if it is unclear.
  4. Until you can update, restrict access to the site or its API paths (for example by IP allowlist or an upstream firewall rule) if it is not meant to be public.
  5. Review User records for unexpected role changes, new administrators or altered credentials, and reset passwords for privileged accounts.
  6. Review other business documents for edits you do not recognize, and restore from a known-good backup if needed.
  7. Rotate API keys and session secrets if you find signs of tampering.
Caution. Updating application code can change behavior or require a restart. Take a backup of the database and files first, and test on a staging copy where you can.

Detection and monitoring

The research does not describe indicators of compromise, so rely on general signs. Look in web server access logs for POST requests to paths containing update_doc from clients that never logged in. This read-only search lists matching lines; the log path is an example, so adjust it for your server.

Search an access log for update_doc requests (adjust the log path)Shell
grep -i "update_doc" /var/log/nginx/access.log

Any hit from an unfamiliar address deserves a closer look, especially if it is followed by a login or role change. Also watch for new privileged accounts and unexplained content changes. If you suspect a compromise, see website hacked: what to do and how to check if a website is hacked. A website firewall can help limit exposure of sensitive endpoints, but it is not a substitute for updating.

What is still unknown

  • No exploitation in the wild is reported in the research, and no CISA KEV listing is shown.
  • No release version number or patched master commit is given.
  • Only one independent publisher covers the story so far, so further technical detail may emerge.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-130071: TridotsTech go1cms master branch through commit 7f68d05 and version-3 branch before commit ead8da3 contains a missing authentication vulnerability in the…nvd.nist.gov ·
  • CVE-2026-130071
  • go1cms
  • TridotsTech
  • missing authentication
  • CMS security