CVE-2026-126123: High severity BeeS Software Solutions ERP vulnerability

Published Nov 10, 2026

Updated

BeeS Software Solutions ERP before 04 September 2026 allows any low-privileged user to navigate directly to the administrative dashboard endpoint and gain access to the administrative console, including unrestricted access to institutional, employee, and student data.

Affected Software

1 affected component

BeeS Software Solutions ERP

Event History

Nov 10, 2026

CVE Published

via NVD·10:18 PM

Data Sourced

via NVD·10:18 PM

DescriptionSeverityWeakness

Frequently Asked Questions

Who can exploit this issue?

Any authenticated low-privileged user of the affected ERP can exploit it. The attacker does not need user interaction and can reach the administrative dashboard directly over the network.

What access could an attacker gain?

A successful attacker can access the administrative console and obtain unrestricted access to institutional, employee, and student data. The provided information does not indicate impacts on data integrity or service availability.

Are installations affected by default?

The available information identifies BeeS Software Solutions ERP versions before 04 September 2026 as affected, but does not state whether a default configuration is required or whether any configuration prevents exploitation.

How can I determine whether my deployment is exposed?

Verify whether the deployment is a BeeS Software Solutions ERP version from before 04 September 2026 and whether a low-privileged account can directly navigate to the administrative dashboard endpoint. Successful access to the administrative console from such an account indicates exposure.

CVE-2026-126123: High severity BeeS Software Solutions ERP vulnerability

Affected Software

Event History

Frequently Asked Questions

Who can exploit this issue?

What access could an attacker gain?

Are installations affected by default?

How can I determine whether my deployment is exposed?

Company

Resources

Contact

Frequently Asked Questions

Who can exploit this issue?

What access could an attacker gain?

Are installations affected by default?

How can I determine whether my deployment is exposed?