dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-14753

HIGH · 7.3 CVSS v3.1 Published 2026-07-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 weeks old

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
A vulnerability was detected in mjperpinosa stumasy up to 327d1b0f2915ba79d7ef8ebb74553e987609d9be. This impacts an unknown function of the file /PHP/objects/notes of the component Note Handler/Assignment Handler. Performing a manipulation of the argument assignment_item_id results in authorization bypass. The attack can be initiated remotely. The exploit is now public and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.

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 · moderate confidence

This is an authorization bypass vulnerability in the mjperpinosa stumasy application where manipulating the assignment_item_id argument in the /PHP/objects/notes component (Note Handler/Assignment Handler) allows bypassing authorization checks. The vulnerability is remotely exploitable and a public exploit exists.

MitigationImplement proper authorization validation for all access to notes/assignments, ensuring the authenticated user has rights to access the specific assignment_item_id before returning any data. Add server-side validation that verifies the current user's permissions match the requested resource.

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

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

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 if stumasy application is installed
    Look for stumasy application files in the web root directory. Common paths include /stumasy/, /stumasy_app/, or search for files containing 'stumasy' in the filename. Use file system search commands like 'find /var/www -iname *stumasy*' or check your web server document root.
    Affected if The stumasy application directory or files exist on the server.
  2. Determine the installed stumasy version
    Check for version files, README files, or configuration files within the stumasy installation that may contain version information. Look in the root directory of the application for files like version.php, README.md, or composer.json that might list the version number.
    Affected if The installed version cannot be determined or is prior to any patched version (no patch version was specified in the provided data).
  3. Locate the vulnerable notes component
    Search for the PHP/objects/notes.php or similar file path within the stumasy application directory. The vulnerable component is at /PHP/objects/notes (Note Handler/Assignment Handler). Use path traversal to find this file.
    Affected if The file PHP/objects/notes.php or similar notes handler exists in the stumasy installation.
  4. Inspect the notes component for authorization logic
    Examine the source code of the notes/assignment handler file. Look for the assignment_item_id parameter handling. Check if there are proper authorization checks before returning assignment or note data. Specifically look for missing checks that verify the authenticated user owns or has permission to access the specific assignment_item_id.
    Affected if The code processes assignment_item_id without verifying user permissions or performs authorization only after returning data.
  5. Test remote accessibility of the vulnerable endpoint
    If the application is web-accessible, attempt to access the /PHP/objects/notes endpoint with manipulated assignment_item_id values. Use a web proxy or curl to send requests with different assignment_item_id parameters and observe if data is returned without proper authorization validation.
    Affected if The endpoint responds to requests with arbitrary assignment_item_id values without requiring or validating user ownership of the assignment.

A user is affected if the stumasy application is installed, the PHP/objects/notes component exists, and the application allows access to assignments via manipulated assignment_item_id values without verifying user permissions.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization validation for all access to notes/assignments, ensuring the authenticated user has rights to access the specific assignment_item_id before returning any data. Add server-side validation that verifies the current user's permissions match the requested resource.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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