/

CVE-2025-67066

Severity:

CRITICAL RISK

(9.8)

SQL Injection (CWE-89) in oasys sysoa Paging Endpoint

CVE-2025-67066

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Remote Database Compromise and Potential Code Execution

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A critical SQL injection vulnerability in oasys sysoa 1.0 affects the outtype parameter used by the /outaddresspaging endpoint. A remote attacker may inject SQL through this parameter and, depending on database permissions and enabled features, execute unauthorized queries or potentially achieve arbitrary code execution.

Affected context

The vulnerability occurs in deployments running oasys sysoa 1.0 with the /outaddresspaging endpoint reachable by an attacker. It becomes risky when the outtype parameter is incorporated into database operations without robust parameterization, validation, or context-aware escaping.

Exploit preconditions

  • Attack surface: Network-accessible /outaddresspaging endpoint
  • Required access: Remote access to submit requests; authentication requirements depend on deployment configuration
  • Trigger point: Processing of the outtype request parameter
  • Why exploitation is possible: Attacker-controlled input may influence a database query without being safely separated from SQL syntax

Why this happens

The underlying bug is an unsafe construction of database queries from externally supplied input. When application data is concatenated into SQL statements or otherwise interpreted as query structure, an attacker may alter the intended operation. This behavior maps to CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection').

Potential impact

  • An attacker may read, modify, or delete database records.
  • The vulnerability could enable authentication or authorization bypass.
  • Sensitive application data may be exposed.
  • Database integrity could be compromised.
  • Arbitrary code execution may be possible if the database account or platform exposes suitable execution capabilities.
  • The application or connected systems could be disrupted.

General mitigation guidance

Mitigation generally focuses on ensuring that user-controlled values cannot become SQL syntax.

Common defensive patterns include:

  • Using parameterized queries or prepared statements for all database operations.
  • Applying allowlist validation for parameters that represent constrained values such as sort or output types.
  • Avoiding dynamic SQL construction where a fixed query or safely mapped query option is sufficient.
  • Running database accounts with the minimum privileges required by the application.
  • Separating database credentials and restricting database features that are not needed by the service.
  • Treating client-side validation as supplemental rather than a security boundary.

How teams detect issues like this

Organizations commonly detect SQL injection risks through:

  • Static analysis rules identifying string concatenation or interpolation in SQL construction.
  • Code review checks for direct use of request parameters in database APIs.
  • Dynamic application testing that uses benign injection probes and observes query errors or unexpected behavior.
  • Web application firewall or API policy rules covering anomalous parameter patterns, used as defense in depth.
  • Database monitoring for unusual query structures, excessive errors, privilege changes, or unexpected data access.
  • Automated security review tools that flag unparameterized query paths.

Sources

SourceLink
github.comgithub.com/lanpan001/OASYS-SQL-injection/blob/main/vulnerability/OASYS%20SQL%20Injection%20Vulnerability.md

Frequently asked

questions

It may be remotely exploitable when the affected endpoint is network-accessible and the attacker can submit requests containing the vulnerable parameter.

Not necessarily. The required access depends on whether the endpoint is public, protected by authentication, or restricted by network controls.

Use parameterized queries or prepared statements, and map constrained request values to a fixed set of server-side query options.

Combine parameterized database access with allowlist validation, least-privilege database accounts, focused code review, static analysis, and monitoring for anomalous database activity.

Find out what's already
exploitable in your codebase.