dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-41464

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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
ProjeQtor versions 7.0 through 12.4.3 contain a missing authorization vulnerability in the objectDetail.php endpoint that allows authenticated users with guest-level privileges to retrieve sensitive data belonging to other users including password hashes and API keys. Attackers can bypass access controls by directly accessing the endpoint without ownership or role-based validation to extract administrator credentials and perform privilege escalation.

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

ProjeQtor versions 7.0 through 12.4.3 have a missing authorization check in the objectDetail.php endpoint that allows authenticated guest-level users to bypass access controls and retrieve sensitive data belonging to other users, including password hashes and API keys, enabling privilege escalation to administrator credentials.

MitigationImplement proper ownership and role-based validation in objectDetail.php to ensure users can only access data they are authorized to view, with explicit denial of guest access to sensitive credential data.

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed ProjeQtor version
    Log into the ProjeQtor admin interface and navigate to Administration > System > About, or check the version displayed on the login page footer. Alternatively, inspect the version parameter in the config file 'configFile.php' or the 'version.php' file in the root directory.
    Affected if The installed version falls within the range 7.0 to 12.4.3 (inclusive).
  2. Verify objectDetail.php endpoint exists
    Locate the file 'objectDetail.php' in the web root directory of the ProjeQtor installation. Check if the file exists and contains the vulnerable code handling sensitive data retrieval.
    Affected if The file exists in the web-accessible directory.
  3. Check if guest or low-privilege authentication is enabled
    Log into ProjeQtor as a guest or basic-level user account (or create one if needed for testing). Verify that the account has only guest-level permissions and can log in successfully.
    Affected if Guest or basic user authentication is enabled and functional.
  4. Test unauthorized access to other user credentials
    Using an authenticated guest-level session, send a crafted request to objectDetail.php requesting data from another user's profile (such as password hashes or API keys). Observe if the endpoint returns sensitive credential information without proper authorization validation.
    Affected if The endpoint returns sensitive data (password hashes, API keys) belonging to other users without proper authorization checks.

A ProjeQtor instance is affected if it runs version 7.0 through 12.4.3, has the objectDetail.php endpoint accessible, and permits guest-level authenticated users to retrieve sensitive credential data from other user accounts.

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

Implement proper ownership and role-based validation in objectDetail.php to ensure users can only access data they are authorized to view, with explicit denial of guest access to sensitive credential data.

Recommended fix Moderate confidence

ProjeQtor version greater than 12.4.3 (contact vendor for exact patched version)

  1. 1. Identify the currently installed ProjeQtor version by checking the version file or admin interface
  2. 2. Confirm the installation falls within versions 7.0 through 12.4.3 which are affected by CVE-2026-41464
  3. 3. Contact ProjeQtor directly or check their official release notes/security advisories at www.projeqtor.com for the patched version
  4. 4. Backup the current ProjeQtor installation and database before upgrading
  5. 5. Upgrade to the latest stable ProjeQtor release that includes the fix for this authorization bypass vulnerability in objectDetail.php
  6. 6. After upgrade, verify that guest-level users can no longer access other users' sensitive data including password hashes and API keys
  7. 7. Consider resetting all user passwords and API keys as a precaution given the sensitivity of exposed credentials
Caveat Review ProjeQtor release notes between your current version and the target version for any breaking changes or migration requirements

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41464 — 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-41464 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