CVE-2026-77767

HighCVSS 7.5

Published: 21/08/2026(UTC)Updated: 21/08/2026(UTC)Translated: 21/08/2026(UTC)NVD NIST

Summary

Reconmap's API applies a fallback authorization policy requiring an authenticated administrator, but the report preview action in ReportsController.cs carries [AllowAnonymous], opting out of that policy. PreviewReport loads the project and linked organisation without any authentication, membership, or role check. Because the id is an auto-increment primary key, an unauthenticated attacker can walk sequential ids to retrieve sensitive details of all projects.

Risk Assessment

An unauthenticated attacker can access confidential information about penetration testing projects and client data, constituting a serious confidentiality breach.

Recommendation

Immediately remove the [AllowAnonymous] attribute from the report preview action or add proper access control, and consider restricting API access.

Other vulnerabilities in Reconmap

CVE-2026-77769Medium
The report.list procedure in Reconmap's trpc package accepted a projectId and a dashboardId, but only verified membership for the supplied projectId, not that the dashboardId belonged to that project. An authenticated user could pair a projectId from their own organization with a dashboardId from another organization and receive every report in that dashboard. A correctly scoped helper, listReportsCore, already existed but was not used by the router.

Original NVD description (English source)

Reconmap's API applies a fallback authorization policy in apps/api/app/Program.cs that requires an authenticated user holding the administrator role, so controllers without their own attribute reject anonymous callers. The report preview action in apps/api/app/Controllers/ReportsController.cs carries [AllowAnonymous] and therefore opts out of that policy. PreviewReport loads the Project row named by the id path segment, loads the linked Organisation through the project's ClientId, and renders both into default-report-template.html, which prints the project name and description together with the client organisation's name, address and URL. No authentication, project membership or role check is performed. Because the id is the auto-increment primary key of the project table, an unauthenticated remote caller can walk sequential ids to retrieve the engagement details and client organisation of every project on the instance, and the 404 returned for a missing id reveals which project ids exist. Reconmap stores penetration-testing engagements, so the disclosed descriptions and client records are sensitive by nature.