dromara orion-visor up to 2.5.7 ExposeApiAspect.java ExposeApiAspect.beforeExposeApi hard-coded credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 1.98+ |
Summary
A vulnerability identified as critical has been detected in dromara orion-visor up to 2.5.7. This affects the function ExposeApiAspect.beforeExposeApi of the file ExposeApiAspect.java. The manipulation leads to hard-coded credentials.
This vulnerability is uniquely identified as CVE-2026-90509. The attack is possible to be carried out remotely. Moreover, an exploit is present.
The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability was found in dromara orion-visor up to 2.5.7 and classified as critical. This issue affects the function ExposeApiAspect.beforeExposeApi of the file ExposeApiAspect.java. The manipulation with an unknown input leads to a hard-coded credentials vulnerability. Using CWE to declare the problem leads to CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. Impacted is confidentiality, integrity, and availability.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-90509. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1110.001 for this issue.
The exploit is available at github.com. It is declared as proof-of-concept. The project was informed of the problem early through an issue report but has not responded yet.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Hard-coded credentialsCWE: CWE-798 / CWE-259 / CWE-255
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
09/12/2026 Advisory disclosed09/12/2026 VulDB entry created
09/12/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 170
Status: Not defined
CVE: CVE-2026-90509 (🔒)
GCVE (CVE): GCVE-0-2026-90509
GCVE (VulDB): GCVE-100-403097
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/12/2026 11:03Changes: 09/12/2026 11:03 (57)
Complete: 🔍
Submitter: summmm
Cache ID: 216::103
Submit
Accepted
- Submit #911864: dromara orion-visor v2.5.7 Default Token (by summmm)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.