CVE-2026-1223VulnerabilityPublished 20 Jan 2026

CVE-2026-1223: BROWAN COMMUNICATIONS PrismX MX100 AP controller · Insufficiently Protected Credentials

Affects BROWAN COMMUNICATIONS PrismX MX100 AP controllerSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium : upgrade to 1.03.23.01 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.03.23.01

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade BROWAN COMMUNICATIONS PrismX MX100 AP controller to 1.03.23.01.

Affected software

Product	Affected	Fixed in
BROWAN COMMUNICATIONSPrismX MX100 AP controller	Affected <1.03.23.01	Fixed in 1.03.23.01

AI-suggested

1. Restrict access to the PrismX MX100 AP controller's web frontend to trusted administrative networks using network segmentation and firewall rules. 2. Enforce strong authentication mechanisms and limit privileged account usage to reduce the risk of credential compromise. 3. Regularly audit and monitor access logs for unusual or unauthorized access attempts to the device management interface. 4. Avoid storing SMTP credentials in the controller where possible; use alternative secure methods for email relay authentication. 5. Implement multi-factor authentication (MFA) for administrative access to the device to add an additional security layer. 6. Once available, promptly apply vendor patches or firmware updates addressing this vulnerability. 7. Educate administrators on the risks of credential exposure and enforce strict password management policies. 8. Consider deploying intrusion detection/prevention systems (IDS/IPS) to detect anomalous activities related to SMTP credential access. 9. Isolate critical network segments to limit the impact of potential credential compromise. 10. Coordinate with BROWAN COMMUNICATIONS support channels for updates and guidance.

Description

PrismX MX100 AP controller developed by BROWAN COMMUNICATIONS has an Insufficiently Protected Credentials vulnerability, allowing privileged remote attackers to allowing authenticated remote attackers to obtain SMTP plaintext passwords through the web frontend.

Impact

For European organizations, this vulnerability poses a risk to the confidentiality of SMTP credentials managed via the PrismX MX100 AP controller. Exposure of these credentials can lead to unauthorized access to email systems, enabling attackers to intercept sensitive communications, conduct phishing campaigns, or move laterally within the network. Organizations relying on this controller for wireless access point management and integrated SMTP services may face increased risk of data breaches. The requirement for privileged authentication limits the threat to insiders or attackers who have already compromised credentials, but the impact remains significant in environments with weak access controls. Critical infrastructure, government agencies, and enterprises with high reliance on secure email communications are particularly vulnerable. The absence of patches means organizations must rely on compensating controls to mitigate risk. Additionally, disclosure of plaintext SMTP passwords can undermine trust in communication channels and potentially violate data protection regulations such as GDPR if personal data is exposed.

CWE-522Insufficiently Protected Credentials (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
Architecture and Design
Use an appropriate security mechanism to protect the credentials.
Architecture and Design
Make appropriate use of cryptography to protect the credentials.
Implementation
Use industry standards to protect the credentials (e.g. LDAP, keystore, etc.).
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V2.10.3 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
Signature Spoofing by Key Theft (opens in a new tab)
Password Recovery Exploitation (opens in a new tab)
Kerberoasting (opens in a new tab)
Modify Existing Service (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Jan 2026, 07:05 UTC

WeaknessesCWE-522

Technical details

References

Community reviews

Related threats