CVE Intelligence
High Logic error exploit reference

CVE-2022-1931 — Incorrect Synchronization in polonel/trudesk

Incorrect Synchronization in GitHub repository polonel/trudesk prior to 1.2.3.

Published May 30, 2022 · Updated Oct 21, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: @huntrdev

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 1.7% (30-day exploitation probability)+12
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
1.75%
ahead of 78% of scored CVEs · Oct 25, 2026
Affects
Polonel
Trudesk
CVSS base
8.1
High · 4 source(s)
Prioritization reference: 9.1 provisional

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — github.com (NIST National Vulnerability Database)
  • Documented patch — huntr.dev (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Polonel Trudesk, Trudesk Project Trudesk).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes matching the vulnerability class (logic error), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Polonel Trudesk < 1.2.3 Vulnerable CVE Program (cve.org) e CISA ADP
Trudesk Project Trudesk < 1.2.3 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.1 CVSS 3.1 High 2.8 5.2 nvd@nist.gov via NIST National Vulnerability Database
8.1 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
9.1 CVSS 3.0 Critical 2.3 6.0 security@huntr.dev via NIST National Vulnerability Database
9.1 CVSS 3.0 Critical — — @huntrdev via CVE Program (cve.org) e CISA ADP
5.5 CVSS 2.0 Medium 8.0 4.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 9.1 (security@huntr.dev via NIST National Vulnerability Database) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-662 · Improper Synchronization

Other CVEs with this weakness →

EPSS over time FIRST

Oct 21, 2026 → Oct 25, 2026 · 5 reading(s) · max 2.09%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · polonel/polonel/trudesk
    Oct 21, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 21, 2026
  • Fix documented
    Oct 21, 2026 · NIST National Vulnerability Database
  • Affected products added · trudesk project/trudesk
    Oct 21, 2026 · NIST National Vulnerability Database
  • CVSS changed · 8.1
    Oct 21, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 21, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 21, 2026 · Alertas do Telegram
  • 2022
  • CVE published
    May 30, 2022 · @huntrdev

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 21, 2026 – Oct 21, 2026
  • 1× Official description updated · Oct 21, 2026 – Oct 21, 2026

References

4 on the record

Elsewhere on this site

Polonel
every CVE for this vendor
Logic error
same class
CWE-662
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-114399 Trudesk through 1.2.11 Path Traversal via Backup Delete and Restore API 4d
  • CVE-2026-114400 Trudesk through 1.2.11 Missing Authentication for Ticket Attachments via /uploads 4d
  • CVE-2026-114401 Trudesk through 1.2.11 Username Enumeration via Regex Injection in /api/v1/login 4d
  • CVE-2026-114402 Trudesk through 1.2.11 Path Traversal and Authorization Bypass via Profile Image Upload 4d
  • CVE-2026-114394 Trudesk through 1.2.11 Authorization Bypass via Ticket Comment and Create APIs 4d
  • CVE-2026-114395 Trudesk through 1.2.11 Authorization Bypass via /api/v1/messages/send 4d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2022-1931 is "Incorrect Synchronization in polonel/trudesk", rated High. It affects Trudesk (Polonel); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.1 describes technical severity. EPSS 1.75% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.