PULSE
FEED
ransomqilin reclama a Insurance Audit Services · US · Financial Servicesransomn0n reclama a Company #137 · CAransomn0n reclama a Company #136 · DKransomn0n reclama a Company #135 · IDransomn0n reclama a Company #134 · USransomn0n reclama a Company #133 · USransomredact reclama a Omni Hotels & Resorts · US · Hospitalityransomakira reclama a Westboro Partnersransomakira reclama a System Plus · Technologyransomakira reclama a David L Wade & Associates · Professional Servicesransomakira reclama a Source Energy Services · CA · Energy & Utilitiesransomaoqin reclama a Sistel · BR · Technologyransombyod reclama a First and Final Warning - IHG Hotels & Resorts (Estate) · Hospitalityransomqilin reclama a Calvary Christian College · AU · Educationransomqilin reclama a Insurance Audit Services · US · Financial Servicesransomn0n reclama a Company #137 · CAransomn0n reclama a Company #136 · DKransomn0n reclama a Company #135 · IDransomn0n reclama a Company #134 · USransomn0n reclama a Company #133 · USransomredact reclama a Omni Hotels & Resorts · US · Hospitalityransomakira reclama a Westboro Partnersransomakira reclama a System Plus · Technologyransomakira reclama a David L Wade & Associates · Professional Servicesransomakira reclama a Source Energy Services · CA · Energy & Utilitiesransomaoqin reclama a Sistel · BR · Technologyransombyod reclama a First and Final Warning - IHG Hotels & Resorts (Estate) · Hospitalityransomqilin reclama a Calvary Christian College · AU · Education
← Todos os CVEs
CVE Watch31 de jul. de 2026

CVE-2022-47966

Zoho ManageEngine Multiple Products Remote Code Execution Vulnerability

CVSS

9.8

Crítica

EPSS

99.8%

p100

KEV

SIM

23 de jan. de 2023

Exploit Today

80

0-100

Publicado: 18 de jan. de 2023 · Última mod.: 31 de jul. de 2026 · CWE-20

EPSS · 30d
99.8%EPSS · 30 dias99.8%
2026-10-082026-11-05
Ficha do catálogo KEV

Produto

Zoho / ManageEngine

Vulnerabilidade

Zoho ManageEngine Multiple Products Remote Code Execution Vulnerability

Adicionado ao KEV

23 de jan. de 2023

Corrigir até

13 de fev. de 2023

Uso conhecido em ransomware

Sim

Descrição resumida

Multiple Zoho ManageEngine products contain an unauthenticated remote code execution vulnerability due to the usage of an outdated third-party dependency, Apache Santuario.

Ação necessária

Apply updates per vendor instructions.

Notas

https://www.manageengine.com/security/advisory/CVE/cve-2022-47966.html; https://nvd.nist.gov/vuln/detail/CVE-2022-47966

Descrição técnica

Multiple Zoho ManageEngine on-premise products, such as ServiceDesk Plus through 14003, allow remote code execution due to use of Apache Santuario xmlsec (aka XML Security for Java) 1.4.1, because the xmlsec XSLT features, by design in that version, make the application responsible for certain security protections, and the ManageEngine applications did not provide those protections. This affects Access Manager Plus before 4308, Active Directory 360 before 4310, ADAudit Plus before 7081, ADManager Plus before 7162, ADSelfService Plus before 6211, Analytics Plus before 5150, Application Control Plus before 10.1.2220.18, Asset Explorer before 6983, Browser Security Plus before 11.1.2238.6, Device Control Plus before 10.1.2220.18, Endpoint Central before 10.1.2228.11, Endpoint Central MSP before 10.1.2228.11, Endpoint DLP before 10.1.2137.6, Key Manager Plus before 6401, OS Deployer before 1.1.2243.1, PAM 360 before 5713, Password Manager Pro before 12124, Patch Manager Plus before 10.1.2220.18, Remote Access Plus before 10.1.2228.11, Remote Monitoring and Management (RMM) before 10.1.41. ServiceDesk Plus before 14004, ServiceDesk Plus MSP before 13001, SupportCenter Plus before 11026, and Vulnerability Manager Plus before 10.1.2220.18. Exploitation is only possible if SAML SSO has ever been configured for a product (for some products, exploitation requires that SAML SSO is currently active).

Referências oficiais
CVEs relacionados
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-715488.8 ALT
—
——0SuiteCRM is an open-source, enterprise-ready Customer Relationship Management (CRM) software application. Prior to 7.15.2 and 8.10.2, AOR_Report::build_report_query_where incorporates a report editor's parameter_value when value_type=Field without sufficient validation. An authenticated user who can save a report can use SQL injection to read the entire SuiteCRM database. Disclosed data can include users.user_hash, OAuth2 tokens, CRM records, report definitions, and configuration data; the connector does not permit stacked queries, so direct write-through-injection is not supported. This issue is fixed in versions 7.15.2 and 8.10.2.7h
CVE-2026-1164722.7 BAI
—
——0A security issue was discovered in ingress-nginx where a user with permission to create an Ingress may be able to cause denial of service of the ingress-nginx data plane, or possibly redirect traffic from other Ingresses. Kubernetes clusters are only affected if they are using ingress-nginx. Due to a missing check, the mirror-target Ingress annotation can be used to target an unauthenticated configuration API within the ingress-nginx controller, allowing write commands to be submitted. Corrupting the data within that configuration API results in all traffic through ingress-nginx being dropped until an Ingress configuration change or a controller restart causes the data to be recreated correctly. In principle, this write access could also be used to redirect traffic from other Ingresses controlled by the same ingress-nginx instance. In practice, there is negligible additional risk: such redirection would require privileged information about internal ingress-nginx state, and users can already redirect traffic from other Ingresses controlled by the same ingress-nginx anyway.7h
CVE-2026-971746.8 MÉD
—
——0A flaw was found in the Client-Initiated Backchannel Authentication (CIBA) implementation of Keycloak. The CIBA endpoint fails to properly validate the sub parameter, allowing it to be stored as an additional request parameter. During the token issuance process, this injected value overwrites the legitimate subject identifier. This allows an attacker to authenticate as themselves but receive security tokens belonging to a different victim user, leading to unauthorized account access.8h
CVE-2026-928578.1 ALT
—
——0Keycloak provides a Dynamic Client Registration feature that allows users with specific tokens to register their own applications. A flaw in how Keycloak validates these registration requests allows an attacker to create a malicious application that forges identity information. By mapping their own user profile details to protected fields like the user ID (sub) or intended audience (aud), an attacker can generate signed security tokens that make them appear to be a different user. This could allow an attacker to impersonate other users or gain unauthorized access to services that rely on these tokens for identity verification.8h
CVE-2026-1231848.1 ALT
—
——0An incorrect authorization vulnerability exists in the Altium 365 Git Service. The permission check performed when a user pushes to a project repository did not correctly evaluate the required access level, so the check passed for any user holding any level of access to the project. As a result, an authenticated user with view-only access to a project could write to that project's git repository. Read access was evaluated correctly and was not affected, and exploitation requires an authenticated account with existing access to the target project. The issue has been remediated in Altium 365 at the service level and no customer action is required. On-premise Altium Enterprise Server is not affected.6h
CVE-2026-102927—
—
——0HedgeDoc is an open source, real-time collaborative markdown notes application. Prior to 1.11.1, the WebSocket permission handler allows a note owner to store strings outside the supported freely, editable, limited, locked, protected, and private permission values. The viewing and editing checks handle only known values and can otherwise fall through to permissive behavior, making a note readable or writable more broadly than intended. SQLite deployments can persist the invalid value because the database column does not strictly enforce the set, while MySQL and PostgreSQL reject the database update but can leave the in-memory note state inconsistent for connected users until reload or cache eviction. Exploitation requires the note owner to intentionally submit an invalid permission value, and the owner could already choose a legitimate permissive setting, which limits the practical security impact. This issue is fixed in version 1.11.1.8h