LiveActive security incident?Get immediate response
CVE Record

CVE-2022-22916: O2OA v6.4.7 was discovered to contain a remote code execution (RCE) vulnerability via /x_program_center/jax...

O2OA v6.4.7 was discovered to contain a remote code execution (RCE) vulnerability via /x_program_center/jaxrs/invoke.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-22916 describes remote code execution in O2OA v6.4.7 through an application endpoint. If an affected instance is reachable by untrusted users, the business risk is potentially serious. The source bundle does not provide CVSS, vendor advisory details, authentication requirements, or confirmed fixed versions.

Executive priority

Prioritize this for rapid exposure review if O2OA is used. Remote code execution can enable system compromise, but the available evidence is incomplete and does not show confirmed active exploitation.

Technical view

The CVE record states O2OA v6.4.7 contains an RCE vulnerability via /x_program_center/jaxrs/invoke. A public GitHub proof-of-concept reference is listed, but the bundle does not include validated exploit mechanics, affected CPEs, CWE mapping, or patch metadata.

Likely exposure

Exposure is limited to organizations running O2OA v6.4.7, especially if the application or named endpoint is internet-accessible or reachable from lower-trust networks. The source bundle does not confirm other affected versions.

Exploitation context

CISA KEV status is false in the bundle, so there is no cited evidence of active exploitation. The referenced public PoC indicates research-level exploit interest, but this should not be treated as confirmed in-the-wild exploitation.

Researcher notes

Key gaps are CVSS, CWE, CPEs, authentication prerequisites, vendor advisory, and fixed-version data. Treat the GitHub PoC reference as public exploitability context, not proof of active exploitation.

Mitigation direction

  • Identify any O2OA v6.4.7 deployments immediately.
  • Check O2OA vendor guidance for fixed versions or official mitigations.
  • Restrict untrusted access to the affected application and endpoint.
  • Increase monitoring for suspicious requests to the named endpoint.

Validation and detection

  • Confirm deployed O2OA versions from asset inventory or application metadata.
  • Review perimeter exposure for O2OA web interfaces.
  • Search logs for requests to /x_program_center/jaxrs/invoke.
  • Verify remediation against vendor guidance when available.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-22916 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
3Timeline events
1ADP providers
2Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.