Security readout for executives and security teams
Plain-English summary
Otalio Ship Property Management System before version 2.22.0 may trust altered login tokens without verifying their signature. A logged-in attacker could impersonate higher privileges, potentially exposing or changing sensitive operational data. The supplied CVSS score is 8.1, reflecting high confidentiality and integrity impact without a stated availability impact.
Executive priority
Treat this as a high-priority identity-control failure. Identify affected installations immediately and schedule prompt upgrades, prioritizing externally reachable or broadly accessible deployments. Because valid low-privileged access is required, also review recent privileged activity for potential account-based abuse.
Technical view
The flaw is CWE-347: improper cryptographic signature verification. A network-accessible, low-privileged authenticated attacker can tamper with JWT claims because affected releases do not validate the token signature. Exploitation requires no user interaction and does not change security scope. The source bundle identifies releases before 2.22.0 as vulnerable.
Likely exposure
Exposure is limited to Otalio Ship Property Management System deployments running versions earlier than 2.22.0. An attacker must already be authenticated, but the vulnerable interface is network-accessible. The sources do not identify affected modules, configurations, deployment prevalence, or whether internet exposure is required.
Exploitation context
The supplied record is not listed in CISA KEV, and the sources provide no evidence of active exploitation. The low complexity and minimal privilege requirement make abuse plausible where an attacker has a valid account. No exploit code, observed campaign, or public weaponization evidence is established by the bundle.
Researcher notes
The narrative clearly sets the vulnerable range as versions before 2.22.0, but the supplied structured affected entry lists only version “0” with default status “unaffected.” This makes machine-readable range interpretation incomplete. Researchers should rely on the narrative cautiously and verify exact applicability with Otalio or the cited Mandiant advisory.
Mitigation direction
- Upgrade affected installations to Otalio Ship Property Management System 2.22.0 or later.
- Confirm the supported remediation path and deployment instructions with Otalio guidance.
- Restrict access to the affected service while upgrades are pending.
- Monitor authenticated activity for unexpected privilege or role changes.
Validation and detection
- Inventory all Otalio Ship Property Management System instances and record their exact versions.
- Confirm no production instance is running a release earlier than 2.22.0.
- Verify the updated service rejects JWTs with invalid signatures in an authorized test environment.
- Review logs for unusual role claims, privilege changes, or sensitive administrative actions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-347: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-9210 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N2.85.2MandiantVulnerability scoring details
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.otalio.com/solutions/CVE reference, Mandiant · product
- https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0023.mdCVE reference, Mandiant · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Verification of Cryptographic Signature
Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.