CVE-2023-31152 [Medium] | Authentication Bypass in Sel-2241 Rtac Module Firmware

An Authentication Bypass Using an Alternate Path or Channel vulnerability in the Schweitzer Engineering Laboratories Real-Time Automation Controller (SEL RTAC) Web Interface allows Authentication Bypass. See SEL Service Bulletin dated 2022-11-15 for more details.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.24%	0.36%	+0.12%
2	2026-06-06	0.05%	0.24%	+0.18%
3	2026-05-11	—	0.05%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.24%

0.36%

+0.12%

2026-06-06

0.05%

0.24%

+0.18%

2026-05-11

—

0.05%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
4.0	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	1.0	2.7	[email protected]
8.8	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

4.0

3.1

MEDIUM

CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

1.0

2.7

[email protected]

8.8

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

5.9

[email protected]

Affected software / configurations for CVE-2023-31152

Vendor	Product	Version	Raw CPE
selinc	sel-2241_rtac_module_firmware	>= r147-v0, < r150-v2	cpe:2.3:o:selinc:sel-2241_rtac_module_firmware::::::::
selinc	sel-3350_firmware	>= r148-v0, < r150-v2	cpe:2.3:o:selinc:sel-3350_firmware::::::::
selinc	sel-3505_firmware	>= r147-v0, < r150-v2	cpe:2.3:o:selinc:sel-3505_firmware::::::::
selinc	sel-3505-3_firmware	>= r147-v0, < r150-v2	cpe:2.3:o:selinc:sel-3505-3_firmware::::::::
selinc	sel-3530_firmware	>= r147-v0, < r150-v2	cpe:2.3:o:selinc:sel-3530_firmware::::::::
selinc	sel-3530-4_firmware	>= r147-v0, < r150-v2	cpe:2.3:o:selinc:sel-3530-4_firmware::::::::
selinc	sel-3532_firmware	>= r147-v0, < r150-v2	cpe:2.3:o:selinc:sel-3532_firmware::::::::
selinc	sel-3555_firmware	>= r147-v0, < r150-v2	cpe:2.3:o:selinc:sel-3555_firmware::::::::
selinc	sel-3560e_firmware	>= r147-v0, < r150-v2	cpe:2.3:o:selinc:sel-3560e_firmware::::::::
selinc	sel-3560s_firmware	>= r147-v0, < r150-v2	cpe:2.3:o:selinc:sel-3560s_firmware::::::::

References for CVE-2023-31152

URL	Tags
https://selinc.com/support/security-notifications/external-reports/	Vendor Advisory
https://www.nozominetworks.com/blog/	Third Party Advisory

URL

CVE-2023-31152 | Authentication Bypass Using an Alternate Path or Channel

Exploit prediction scoring system (EPSS) score for CVE-2023-31152

Common vulnerability scoring system (CVSS) metrics for CVE-2023-31152

Weakness enumeration for CVE-2023-31152

Affected software / configurations for CVE-2023-31152

References for CVE-2023-31152