dbcve.org
Api OrchestratorApplication · Netaxis

CVE-2022-23851

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-17
Fix available
A fix is available. Upgrade to 0.19.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Server-Side Template Injection (SSTI) vulnerability in Netaxis API Orchestrator versions prior to 0.19.3. The vulnerability allows attackers to inject malicious template code that can be executed server-side, potentially leading to remote code execution (RCE). Given the CVSS score of 9.8, this is exploitable over the network without authentication and results in complete system compromise.

MitigationUpgrade to API Orchestrator version 0.19.3 or later. If immediate upgrading is not possible, disable or restrict template rendering functionality and implement input validation/sanitization on all user-supplied template variables.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Api OrchestratorApplication
Affected:< 0.19.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Netaxis API Orchestrator is installed
    Search for APIO installation directories, services, or process listings containing 'apio', 'api-orchestrator', or 'netaxis'. Check common installation paths or use package managers if used for deployment.
    Affected if Netaxis API Orchestrator is found running in the environment
  2. Determine the installed APIO version
    Locate the version file, startup script, or JAR/WAR manifest that contains the version number. Check the application banner at startup or query the API if a version endpoint exists.
    Affected if The version is found to be lower than 0.19.3 (e.g., 0.19.2, 0.18.x, etc.)
  3. Verify template engine is enabled
    Inspect the APIO configuration files (e.g., application.properties, config.yaml, or similar) for template engine settings. Look for template rendering, view resolution, or template engine configuration sections.
    Affected if A server-side template engine is configured and active in the APIO deployment
  4. Check for exposed template input endpoints
    Review APIO routing configuration or reverse proxy settings to identify endpoints that accept user input and pass it to the template engine. Look for endpoints handling dynamic content rendering.
    Affected if Endpoints exist that accept user-supplied input and process it through the template engine without sanitization

The environment is affected if Netaxis API Orchestrator is running with a version lower than 0.19.3 and user input can reach the server-side template engine.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.19.3 or later
Fixed in 0.19.3
Interim mitigation

Upgrade to API Orchestrator version 0.19.3 or later. If immediate upgrading is not possible, disable or restrict template rendering functionality and implement input validation/sanitization on all user-supplied template variables.

Recommended fix High confidence

0.19.3

  1. 1. Back up your current API Orchestrator configuration and data
  2. 2. Review the official release notes for version 0.19.3 to understand any changes
  3. 3. Download API Orchestrator version 0.19.3 or later from the official vendor source
  4. 4. Install the upgrade following the vendor's standard upgrade procedure
  5. 5. Verify the installation completed successfully
  6. 6. Test that the API Orchestrator functionality is working as expected
  7. 7. Confirm the SSTI vulnerability is no longer present by reviewing fixed template handling

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Api Orchestrator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,920.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23851 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-23851 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data