HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members
  • Sponsor HOL
  • Advertise with HOL

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorFund agreed research, implementation and shared testing through the HOL Partner Program.
  • AdvertiseCompare README logo placements, previews and monthly prices, or promote a plugin or extension.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 77132 typo3 cms information disclosure via backend
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Sponsor
  • Advertise
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
Medium · CVSS 5.3CVE-2026-77132

TYPO3 CMS - Information Disclosure via Backend Localization WizardCVE-2026-77132

Answer in brief

CVE-2026-77132 records a Medium severity (CVSS 5.3) vulnerability in TYPO3 CMS - Information Disclosure via Backend Localization Wizard. The current sources do not mark it as known exploited. The current feed maps TYPO3/TYPO3 CMS (generic), TYPO3/typo3/cms-backend (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 8, 2026Updated Sep 8, 2026Source checked Oct 23, 2026First seen by HOL Sep 8, 2026Material review Sep 8, 2026
Upstream Advisory

Key facts

Risk
Medium · CVSS 5.3
Exploitation
Not marked as known exploited
Affected software
2 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps TYPO3/TYPO3 CMS (generic), TYPO3/typo3/cms-backend (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
TYPO3/TYPO3 CMSgeneric>=10.0.0 <10.4.60 || >=11.0.0 <11.5.54 || >=12.0.0 <12.4.49 || >=13.0.0 <13.4.35 || >=14.0.0 <14.3.710.4.60, 11.5.54, 12.4.49, 13.4.35, 14.3.7
TYPO3/typo3/cms-backendgeneric>=10.0.0 <10.4.60 || >=11.0.0 <11.5.54 || >=12.0.0 <12.4.49 || >=13.0.0 <13.4.35 || >=14.0.0 <14.3.710.4.60, 11.5.54, 12.4.49, 13.4.35, 14.3.7

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for TYPO3/TYPO3 CMS, TYPO3/typo3/cms-backend.
  2. 2Review the reported fix. Update TYPO3/TYPO3 CMS to 10.4.60; TYPO3/typo3/cms-backend to 10.4.60 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 8, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  2. Source modified

    Sep 8, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  3. First seen by HOL

    Sep 8, 2026

Sources and claim methodology

  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • Source referencenews.typo3.com
Upstream source description

It has been discovered that several AJAX routes used for the backend localization wizard failed to perform authorization checks. This allowed authenticated, low-privileged backend users to access information about records and content elements that fall outside of their permitted range. Exploiting this vulnerability requires a low-privileged backend user account. This issue affects TYPO3 CMS versions 10.0.0-10.4.59, 11.0.0-11.5.53, 12.0.0-12.4.48, 13.0.0-13.4.34 and 14.0.0-14.3.6.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • DJI CrystalSky ZS600C android.dji.server binder transaction 1018 command injection as rootAlso CWE-862
  • DJI CrystalSky ZS600C DJIUpdateService binder exposes privileged operations without authorizationAlso CWE-862
  • baserCMS: Path traversal in the BcThemeFile admin screen allows file disclosureAlso CWE-200
  • odhcpd DHCPv6 Short IA_NA/IA_PD Body Stack DisclosureAlso CWE-200
  • Customer Order Data Exposed via Unauthenticated gtm_server_side_order_id Cookie Manipulation in GTM Server Side WordPress PluginAlso CWE-200
  • Zimbra Collaboration Suite Missing Authorization in ConfigureZimlet Enables Delegated Administrator Privilege EscalationAlso CWE-862

Record context

Vulnerability class
Missing Auth
EPSS
Not reported
CWE IDs
CWE-862, CWE-200
Source
CVE List V5
Source checked
Oct 23, 2026
References
4 linked sources
Open source record