PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-90509 dromara CVE debrief

A weakness has been identified in dromara orion-visor up to 2.5.7. Affected by this issue is the function ExposeApiAspect.beforeExposeApi of the file ExposeApiAspect.java. Executing a manipulation can lead to hard-coded credentials. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

Vendor
dromara
Product
orion-visor
CVSS
MEDIUM 5.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-13
Original CVE updated
2026-09-20
Advisory published
2026-09-13
Advisory updated
2026-09-20

Who should care

Defenders responsible for dromara orion-visor deployments should assess exposure and prioritize verification of affected versions. Defenders should also consider the potential impact on their organization's security posture and take steps to mitigate the risk.

Why it matters

Defenders should prioritize verifying the presence of affected versions and assessing exposure, as the exploit has been made public and can lead to hard-coded credentials.

  • Verify the presence of affected versions in your environment
  • Assess exposure to the vulnerability
  • Implement compensating controls to mitigate the risk
  • Monitor for potential attacks using the public exploit

Technical summary

The function ExposeApiAspect.beforeExposeApi in the file ExposeApiAspect.java of dromara orion-visor up to 2.5.7 is affected by a weakness that can lead to hard-coded credentials. The attack can be executed remotely, and the exploit has been made available to the public. Defenders should prioritize verifying the presence of affected versions and assessing exposure, as the exploit has been made public and can lead to hard-coded credentials. Defenders responsible for dromara orion-visor deployments should assess exposure and prioritize verification of affected versions.

Defensive priority

Defenders should prioritize verifying the presence of affected versions and assessing exposure, as the exploit has been made public.

Recommended defensive actions

  • Verify the presence of affected versions in your environment
  • Assess exposure to the vulnerability
  • Implement compensating controls to mitigate the risk
  • Monitor for potential attacks
  • Review vendor guidance for updates or mitigations
  • Track exceptions and retest remediated assets
  • whoShouldCare

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but the vendor has not responded to the issue report. The exploit has been made public, increasing the risk of attacks. Defenders should verify the presence of affected versions and assess exposure. The weakness is in the function ExposeApiAspect.beforeExposeApi of the file ExposeApiAspect.java in dromara orion-visor up to 2.5.7, leading to hard-coded credentials.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-90509 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-90509

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-90509 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-90509

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.