dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-42291

MEDIUM · 6.8 CVSS v3.1 Published 2026-05-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SysReptor is a fully customizable pentest reporting platform. From version 2026.4 to before version 2026.27, the endpoints for reading and creating sharing links for personal notes is not properly authorized. This allows authenticated attackers who obtain the note ID of victim users to list and create sharing links to those users' personal notes. This gives attackers read and write access to notes of other users. This exploit works in both SysReptor Professional and Community. In Community it has, however, no impact because all users have superuser permissions and can list personal notes of other users at /admin/pentests/usernotebookpage/. This issue has been patched in version 2026.27.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability in SysReptor where the endpoints for reading and creating sharing links on personal notes lack proper authorization checks. Authenticated attackers who obtain a note ID can list and create sharing links to other users' personal notes, granting themselves read and write access.

MitigationUpgrade SysReptor to version 2026.27 or later. In Community edition, the issue has no practical impact since all users already have superuser permissions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed SysReptor version
    Check the SysReptor version file or API endpoint that returns version information. Common locations include the admin interface, a /api/version endpoint, or the docker container labels.
    Affected if The installed version is earlier than 2026.27 and the user is on an edition where not all users have superuser permissions.
  2. Determine user permission levels in the system
    Review user accounts in the SysReptor admin panel to identify whether regular users exist with non-superuser permissions. In Community edition, verify if all accounts are configured as superusers.
    Affected if Non-superuser accounts exist and the SysReptor version is below 2026.27, indicating the IDOR could allow unauthorized access to other users' notes.
  3. Verify the sharing link API endpoints exist and are accessible
    Examine the API documentation or network traffic to identify endpoints related to sharing links (typically under /api/notes/{id}/sharing/ or similar paths).
    Affected if The sharing link functionality endpoints are present in the installation.
  4. Test for authorization gaps on sharing link endpoints
    Using an authenticated non-superuser account, attempt to access or create sharing links for a note owned by a different user by directly referencing the note ID in the API request.
    Affected if Requests succeed without returning 403 Forbidden, indicating the authorization check is missing.

You are affected if SysReptor version is below 2026.27 AND your installation has users without superuser permissions who could exploit the missing authorization on sharing link endpoints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade SysReptor to version 2026.27 or later. In Community edition, the issue has no practical impact since all users already have superuser permissions.

Recommended fix High confidence

2026.27

  1. 1. Back up your current SysReptor installation and database before upgrading
  2. 2. Consult the official SysReptor upgrade documentation for your deployment method (Docker, pip, etc.)
  3. 3. Upgrade to version 2026.27 or later
  4. 4. After upgrading, verify that the authorization checks are working correctly by testing that users cannot access other users' personal notes without proper permissions
  5. 5. Review audit logs if available to check for any suspicious access to personal notes that occurred before the patch
Caveat The description does not mention any breaking changes; upgrade should be straightforward

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42291 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42291 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data