Skip to main content
VulnerabilityPublished

CVE-2025-44033: SQL Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

Given the absence of an official patch, European organizations should prioritize immediate risk reduction strategies. These include: 1) Implementing Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the allDirector() method or related endpoints; 2) Conducting thorough code reviews and applying input validation and parameterized queries or prepared statements in the affected codebase to eliminate injection vectors; 3) Restricting database user privileges to the minimum necessary to limit the impact of potential exploitation; 4) Monitoring application logs and network traffic for anomalous SQL queries or suspicious activity indicative of exploitation attempts; 5) Isolating and segmenting systems running oa_system oasys to contain potential breaches; 6) Engaging with the vendor or development community for updates or patches and applying them promptly once available; 7) Educating development and security teams about secure coding practices to prevent similar vulnerabilities in the future.

Description

SQL injection vulnerability in oa_system oasys v.1.1 allows a remote attacker to execute arbitrary code via the allDirector() method declaration in src/main/java/cn/gson/oasys/mappers/AddressMapper.java

References

Community reviews

Loading reviews…