aaPanel BillionMail up to 4.9 Relay Configuration API relay.go helo_name injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00+ |
Summary
A vulnerability was found in aaPanel BillionMail up to 4.9. It has been rated as critical. This affects an unknown part of the file core/api/relay/v1/relay.go of the component Relay Configuration API. The manipulation of the argument helo_name leads to injection. This vulnerability is traded as CVE-2026-124579. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability, which was classified as critical, has been found in aaPanel BillionMail up to 4.9. This issue affects an unknown function of the file core/api/relay/v1/relay.go of the component Relay Configuration API. The manipulation of the argument helo_name with an unknown input leads to a injection vulnerability. Using CWE to declare the problem leads to CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability.
The advisory is shared at gist.github.com. The identification of this vulnerability is CVE-2026-124579. The exploitation is known to be easy. The attack may be initiated remotely. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1055 for this issue.
The exploit is available at gist.github.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way.
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
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.4
VulDB Temp Score: 7.0
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: InjectionCWE: CWE-74 / CWE-707 / CWE-20
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
11/08/2026 Advisory disclosed11/08/2026 VulDB entry created
11/08/2026 VulDB entry last update
Sources
Advisory: gist.github.comStatus: Confirmed
CNA: VulDB
CVE: CVE-2026-124579 (🔒)
GCVE (CVE): GCVE-0-2026-124579
GCVE (VulDB): GCVE-100-432929
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 11/08/2026 18:13Changes: 11/08/2026 18:13 (57)
Complete: 🔍
Submitter: silverdragon
Cache ID: 216::103
Submit
Accepted
- Submit #1038400: BillionMail <=v4.9 Authenticated RCE (by silverdragon)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.