WEBCON BPS Updates Fix Vacation-Data Authorization Bypass

P2 — VALIDATE AND UPDATEMedium · 5.3 (CVSS v4.0)EXPLOITATION: NOT STATED

Quick Answer

The authority published CVE-2026-92419 for WEBCON BPS 2024.1.1.145 before 2025.2.1.177 and 2026.1.1.1 before 2026.1.1.20. WEBCON BPS is vulnerable to Insecure Direct Object Reference (IDOR) in the /api/vacations/{path} endpoint. The selectedPeople parameter in the Gantt vacation chart API does not validate whether the requesting user is authorized to access the requested users' data. An authenticated attacker can supply arbitrary user logins in the selectedPeople parameter to view vacation schedules of other employees, including managers and staff from other offices, regardless of business logic access restrictions, resulting in unauthorized disclosure of sensitive scheduling information.This vulnerability was fixed in versions: 2025.2.1.177 and 2026.1.1.20 Affected deployments should be matched to the authority's exact scope and moved to the supported fixed release.

Confirm Scope And Apply The Supported Fix

What to do now: Inventory WEBCON BPS 2024.1.1.145 before 2025.2.1.177 and 2026.1.1.1 before 2026.1.1.20, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.

Open the authoritative advisory

Last verified: 2026-09-23 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeWEBCON BPS 2024.1.1.145 before 2025.2.1.177 and 2026.1.1.1 before 2026.1.1.20
AdvisoryCVE-2026-92419
CVECVE-2026-92419
Authoritative release date2026-09-23 14:41:08.125 UTC
Authority revision date2026-09-23 15:20:11.492 UTC
Affected versionsWEBCON BPS 2024.1.1.145 before 2025.2.1.177 and 2026.1.1.1 before 2026.1.1.20
Fixed versionWEBCON BPS 2025.2.1.177 or 2026.1.1.20
CVSS base score5.3 (CVSS v4.0)
CVSS severityMedium
Exploitation statusNot stated by the authority; no exploitation claim is inferred.

What Changed

WEBCON BPS is vulnerable to Insecure Direct Object Reference (IDOR) in the /api/vacations/{path} endpoint. The selectedPeople parameter in the Gantt vacation chart API does not validate whether the requesting user is authorized to access the requested users' data. An authenticated attacker can supply arbitrary user logins in the selectedPeople parameter to view vacation schedules of other employees, including managers and staff from other offices, regardless of business logic access restrictions, resulting in unauthorized disclosure of sensitive scheduling information.This vulnerability was fixed in versions: 2025.2.1.177 and 2026.1.1.20

What To Validate Now

  1. Inventory. Locate WEBCON BPS 2024.1.1.145 before 2025.2.1.177 and 2026.1.1.1 before 2026.1.1.20 deployments, versions, enabled features, exposure paths, owners, and dependent services.
  2. Establish applicability. Compare each deployment with the authority's affected-version statement: WEBCON BPS 2024.1.1.145 before 2025.2.1.177 and 2026.1.1.1 before 2026.1.1.20 Do not infer applicability from product family or severity alone.
  3. Remediate. Apply WEBCON BPS 2025.2.1.177 or 2026.1.1.20 through the supported vendor or project channel, following the current advisory and change-control requirements.
  4. Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.