Secuno
ENNL
Book demo

CVE-2026-92793

8.1 HIGH
  1. Published16 Sept 2026

Description

GoAdmin through 1.2.26 fails to properly anchor the logout pattern when checking permissions, allowing authenticated users to bypass permission checks by appending a query parameter. Attackers can append a query string containing the admin prefix followed by /logout to reach administrative endpoints and perform unauthorized actions including reading sensitive data and modifying application state.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredLow
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-928018.8
cc-connect through 1.5.0 fails to enforce per-user allowlist filtering in the…
CVE-2026-927968.8
Manticore Search versions 27.0.0 before 28.4.4 fail to validate permissions for all…
CVE-2026-927888.8
Coze Studio through 0.5.1 fails to validate that table names in workflow SQL…
CVE-2026-927828.1
Chroma through 1.5.9 fails to validate tenant and database segments when resolving…
CVE-2026-927768.1
Wiki.js through 2.5.314 fails to require path separators when matching START and END…
CVE-2026-275528.1
A low-privileged remote attacker can exploit improper authorization in the…

Frequently asked

Is CVE-2026-92793 being actively exploited?

CVE-2026-92793 is not in the CISA KEV catalog.

How severe is CVE-2026-92793?

CVE-2026-92793 has a CVSS 3.1 base score of 8.1, rated high.

How do I fix CVE-2026-92793?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-92793 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.