Security readout for executives and security teams
Plain-English summary
A critical SQL injection flaw is reported in OASYS sysoa 1.0. An unauthenticated remote attacker may manipulate the outtype parameter, potentially exposing or altering data, disrupting service, and—according to the CVE description—executing arbitrary code. Organizations operating this application should treat reachable instances as urgent.
Executive priority
Prioritize immediate inventory and exposure reduction. Internet-reachable instances warrant emergency handling because the reported impact is complete system compromise without authentication. If exposure is internal-only, still remediate urgently and review logs. No official fix is identified in the supplied sources.
Technical view
CVE-2025-67066 is classified as CWE-89 in the /outaddresspaging path through the outtype parameter. Its CVSS 3.1 score is 9.8, reflecting network reachability, low attack complexity, no required privileges or user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most concerning where OASYS sysoa 1.0 serves /outaddresspaging to untrusted networks. The structured affected-product data is unspecified, so organizations should confirm product identity and version locally rather than relying solely on automated CPE matching.
Exploitation context
The supplied record is not in CISA KEV and provides no cited evidence of active exploitation. A public vulnerability write-up exists, which may increase awareness. This assessment does not establish widespread scanning, reliable exploitation, or confirmed compromise.
Researcher notes
The record reports SQL injection leading to arbitrary code execution, but the supplied structured affected entries list vendor, product, and versions as n/a. The title and description identify OASYS sysoa 1.0. Confirm these details against the application and maintainer before broad vulnerability assertions.
Mitigation direction
- Identify OASYS sysoa 1.0 deployments and determine whether /outaddresspaging is externally reachable.
- Check maintainer guidance for an official patch or supported upgrade; none is identified in the supplied sources.
- Restrict access to the affected path until remediation is available and validated.
- Apply monitored SQL-injection filtering as an interim control, without treating it as a permanent fix.
- Limit the application's database permissions and investigate any unnecessary code-execution capability.
Validation and detection
- Confirm the deployed product and version because the structured affected-product fields are unspecified.
- Verify whether unauthenticated users can reach /outaddresspaging from untrusted networks.
- Review application, proxy, WAF, and database logs for unusual outtype values or SQL errors.
- After remediation, perform authorized non-destructive testing to confirm malicious input is rejected or safely parameterized.
- Confirm compensating controls cover every application instance and network entry point.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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 lookupExecution 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 lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-67066 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.