CVE-2026-130857
EveryDocs Core before 1.6.1 contains an authorization bypass vulnerability that allows authenticated users to access other users' records th
CVSS
8.3
Alta
EPSS
—
KEV
—
Exploit Today
—
0-100
Publicado: 17 de nov. de 2026 · Última mod.: 17 de nov. de 2026 · CWE-639
Ainda não há histórico EPSS suficiente.
EveryDocs Core before 1.6.1 contains an authorization bypass vulnerability that allows authenticated users to access other users' records through unscoped Model.find(params[:id]) lookups in multiple controllers. Self-registered attackers can enumerate sequential ids to read, modify, or delete other users' documents and stored files, and rename or delete their folders, tags and people.
- github.comhttps://github.com/jonashellmann/everydocs-core/blob/v1.6.0/app/controllers/documents_controller.rb#L110-L140
- github.comhttps://github.com/jonashellmann/everydocs-core/commit/4b6e1a79baae44c479505674f9354a9da0906f4d
- github.comhttps://github.com/jonashellmann/everydocs-core/releases/tag/v1.6.1
- github.comhttps://github.com/jonashellmann/everydocs-core/security/advisories/GHSA-g83j-767p-v5w7
- www.vulncheck.comhttps://www.vulncheck.com/advisories/everydocs-core-before-1.6.1-authorization-bypass-via-unscoped-record-lookups
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-68918——
———Ikaros is a content management system for ACGMN media. Prior to 1.2.0, server/src/main/java/run/ikaros/server/core/tag/TagEndpoint.java does not enforce tag ownership for authenticated users with tag permissions. GET /tags/condition accepts an arbitrary userId and can enumerate another user's tags, DELETE /tag/id/{id} deletes a tag without comparing its owner to the requester, and DELETE /tag/condition omits userId from its filter and can delete every user's tags matching the supplied condition. This issue is fixed in version 1.2.0.7hCVE-2026-1308726.5 MÉD—
———Pytition before 2.10 contains an insecure direct object reference vulnerability in the show_signatures view that allows registered users to delete other petitions' signatures by supplying foreign signature IDs. Attackers can post sequential signature IDs to their own petition's signatures page to permanently delete signatures from any user-owned petition and trigger confirmation emails to other signers.8hCVE-2026-1308644.3 MÉD—
———Coyote before commit d6e8fb9 contains a missing authorization vulnerability in Wiki\CommentController::save that allows authenticated users to edit other users' wiki comments. Attackers can send POST requests to /Comment/Save/{wiki}/{id} with another user's comment id, bypassing the WikiCommentPolicy update check, so altered text appears under the original author's name.8hCVE-2026-1308595.4 MÉD—
———Habitat through 1.7.1 contains an insecure direct object reference vulnerability in CreatePostController::addAttachmentsToPost() that allows authenticated users to claim other users' unposted image uploads. Email-verified attackers can submit sequential attachmentIds when creating a post to attach another user's pending image, exposing it publicly and removing it from the uploader's post.5hCVE-2026-1308517.1 ALT—
———wishthis through 1.2.3 contains an authorization bypass vulnerability in User::ownsWishlist() that allows authenticated users to modify other users' wishes and wishlists. Attackers can supply sequential wish_id and wishlist_id values to the wishes and wishlists API handlers to edit wishes, add wishes, or rename and delete wishlists.5hCVE-2026-1306227.1 ALT—
———Incorrect authorization in the credential loading logic in AWS Private CA Connector for Kubernetes (aws-privateca-issuer) before 1.12.0 might allow an authenticated remote user with permission to create namespace-scoped issuers to obtain certificates, including subordinate CA certificates, signed by another namespace's AWS Private CA with that namespace's stored AWS credentials, via a namespace-scoped issuer that references a credentials Secret in that namespace.
To remediate this issue, users should first copy any credentials Secret they intend a namespace-scoped issuer to use into that issuer's namespace and update the issuer's secretRef.namespace to match. Then, upgrade aws-privateca-issuer to version 1.12.0 or the AWS Private CA Connector for Kubernetes EKS add-on to version v1.12.0-eksbuild.1.8h