CVE-2026-22239

Email Sending Vulnerability in BLUVOYIX

Published Jan 14, 2026 CVSS 4.0 · 10 Critical EPSS < 1% KEV · Not listed
Description
The vulnerability exists in BLUVOYIX due to design flaws in the email sending API. An unauthenticated remote attacker could exploit this vulnerability by sending specially crafted HTTP requests to the vulnerable email sending API. Successful exploitation of this vulnerability could allow the attacker to send unsolicited emails to anyone on behalf of the company.

Analysis

AI-generated

Technical impact

The identified flaw resides in the email sending interface of BLUVOYIX. An unauthenticated remote actor can craft HTTP requests targeted at the email API. By triggering this entry point, the application will relay the supplied message to any recipient, effectively allowing the attacker to send unsolicited or potentially malicious emails on behalf of the organization. The absence of authentication checks removes the requirement for elevated privileges, giving the adversary broad reach to any user address stored in or reachable by the system.

Affected Systems

The impacted product is Bluspark Global’s BLUVOYIX email platform. No specific version information is provided, so all deployed instances should be treated as vulnerable until a patch or advisory is released by the vendor.

Risk and Exploitability

The CVSS base score of 10 underscores the critical nature of this vulnerability, while an EPSS score of less than 1% indicates a very low likelihood of immediate exploitation in the wild. Nevertheless, because the flaw allows an attacker to send arbitrary emails without credentials, it poses a serious threat to the organization’s reputation and could serve as a conduit for phishing or spam campaigns. The vulnerability is not currently listed in CISA’s Known Exploited Vulnerabilities catalog, which suggests no publicly documented exploits yet. Exploitation prerequisites are minimal: the attacker simply needs to reach the exposed API endpoint over HTTP, forming a crafted request. No additional software or privileged access is required.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply vendor patch for BLUVOYIX as soon as released.
  • Add input validation and rate limiting on the email‑sending API to address the uncontrolled resource consumption flaw (CWE‑400).
  • Restrict external access to the email‑sending API with firewall rules or network segmentation.
  • Monitor outbound email traffic for abnormal or bulk patterns that may indicate abuse.

Generated by OpenCVE AI on April 18, 2026 at 16:18 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
References
History
Type Values Removed Values Added
First Time appeared Blusparkglobal
Blusparkglobal bluvoyix
Weaknesses NVD-CWE-noinfo
CPEs cpe:2.3:a:blusparkglobal:bluvoyix:-:*:*:*:*:*:*:*
Vendors & Products Blusparkglobal
Blusparkglobal bluvoyix
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}

Type Values Removed Values Added
First Time appeared Bluspark Global
Bluspark Global bluvoyix
Vendors & Products Bluspark Global
Bluspark Global bluvoyix
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description The vulnerability exists in BLUVOYIX due to design flaws in the email sending API. An unauthenticated remote attacker could exploit this vulnerability by sending specially crafted HTTP requests to the vulnerable email sending API. Successful exploitation of this vulnerability could allow the attacker to send unsolicited emails to anyone on behalf of the company.
Title Email Sending Vulnerability in BLUVOYIX
Weaknesses CWE-400
References
Metrics cvssV4_0

{'score': 10, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/RE:H/U:Amber'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
MHV
Published
Updated
Jan 14, 2026, 2:56 PM
Reserved
Jan 6, 2026, 11:20 PM
Status
Analyzed
Published
Jan 14, 2026, 3:16 PM
Modified
Jun 17, 2026, 10:19 AM