LiveActive security incident?Get immediate response
CVE Record

CVE-2022-23851: Netaxis API Orchestrator (APIO) before 0.19.3 allows server side template injection (SSTI).

Netaxis API Orchestrator (APIO) before 0.19.3 allows server side template injection (SSTI).

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Netaxis API Orchestrator (APIO) versions before 0.19.3 are reported vulnerable to server-side template injection. The CVSS score is critical because the issue is network-reachable, requires no authentication, and can affect confidentiality, integrity, and availability. Organizations using APIO should treat version verification and remediation as urgent.

Executive priority

Prioritize this as an urgent remediation item if APIO is used. The vulnerability is rated critical and does not require authentication or user interaction. Business risk depends on whether APIO is deployed and reachable.

Technical view

CVE-2022-23851 is a CWE-1336 server-side template injection issue in Netaxis APIO before 0.19.3. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, score 9.8. The source bundle does not provide CPEs or detailed vulnerable configuration data.

Likely exposure

Exposure is likely limited to organizations running Netaxis APIO earlier than 0.19.3. Risk is highest where APIO is reachable from untrusted networks. The provided CVE data does not include CPEs or deployment-specific indicators.

Exploitation context

The CVE is not listed as KEV in the provided data, so active exploitation is not established here. However, the unauthenticated, network-reachable CVSS vector indicates high exploitability if a vulnerable APIO instance is accessible.

Researcher notes

The public metadata identifies APIO before 0.19.3 and CWE-1336 but lacks CPEs and detailed affected configurations. A referenced researcher blog is listed, but this take does not rely on exploit mechanics or provide reproduction steps.

Mitigation direction

  • Inventory Netaxis APIO deployments and identify their running versions.
  • Upgrade APIO installations before 0.19.3 to 0.19.3 or later.
  • If immediate upgrade is not possible, restrict APIO access to trusted networks.
  • Check Netaxis guidance for any additional vendor-specific remediation steps.
  • Monitor APIO logs for unusual template errors or unexpected unauthenticated requests.

Validation and detection

  • Confirm whether Netaxis APIO is installed in the environment.
  • Record APIO version numbers and flag any version before 0.19.3.
  • Verify externally reachable APIO instances are not exposed to untrusted networks.
  • Confirm the upgrade or compensating access controls are in place.
  • Review application logs for suspicious activity around exposed APIO endpoints.
Prepared
Confidence
medium
Sources
4

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.

cwe · low confidence lookup

CWE-1336: 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 lookup
cve · low confidence lookup

CVE-2022-23851 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

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

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-23851Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-1336 · source CWE mapping

Improper Neutralization of Special Elements Used in a Template Engine

Improper Neutralization of Special Elements Used in a Template Engine represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.