2368 matches found
CVE-2026-106430
The MongoDB C++ Driver is vulnerable to query and rename target confusion due to embedded NUL truncation . The driver discards content following a NUL byte in specific field and collection names accepted by the collection API , leading to a discrepancy between how the driver and the calling appli...
Query and rename target confusion via embedded NUL truncation in MongoDB C++ Driver
The MongoDB C++ Driver discards content after an embedded NUL byte in certain field and collection names accepted by the collection API. This can cause the driver and the calling application to interpret the same name differently. An authenticated actor who can influence a name passed by an...
PT-2026-108136
Name of the Vulnerable Software and Affected Versions MongoDB C++ Driver affected versions not specified Description The MongoDB C++ Driver discards content following an embedded NUL byte in specific field and collection names processed by the collection API. This behavior allows the driver and t...
PT-2026-108265
Name of the Vulnerable Software and Affected Versions Jivejdon versions prior to 5.1 Description Cross-site request forgery CSRF occurs when an attacker tricks an authenticated user into performing unwanted actions. The software allows remote attackers to execute state-changing actions by abusing...
CVE-2026-105268
A flaw was found in Gitea. The Application Programming Interface API endpoints handling issue attachments improperly process attachments associated with comments on that issue. An authenticated user who created an issue can exploit this flaw to rename or delete attachments posted by other users i...
CVE-2026-105268
The Gitea API routes for issue attachments /api/v1/repos/owner/repo/issues/index/assets/attachmentid also accepted attachments that belong to comments on the issue. Because the author of an issue may edit and delete the issue's attachments, a user who opened an issue could rename or delete...
CVE-2026-105268
The Gitea application contains an authorization flaw in its issue attachment API routes (/api/v1/repos/{owner}/{repo}/issues/{index}/assets/{attachment_id}). The vulnerability allows a user who opened an issue to rename or delete attachments that were actually posted in comments by other users. T...
EUVD-2026-94064
The Gitea API routes for issue attachments /api/v1/repos/owner/repo/issues/index/assets/attachmentid also accepted attachments that belong to comments on the issue. Because the author of an issue may edit and delete the issue's attachments, a user who opened an issue could rename or delete...
CVE-2026-105268 Gitea issue attachment API allows changing comment attachments
The Gitea API routes for issue attachments /api/v1/repos/owner/repo/issues/index/assets/attachmentid also accepted attachments that belong to comments on the issue. Because the author of an issue may edit and delete the issue's attachments, a user who opened an issue could rename or delete...
CVE-2026-105268 Gitea issue attachment API allows changing comment attachments
The Gitea API routes for issue attachments /api/v1/repos/owner/repo/issues/index/assets/attachmentid also accepted attachments that belong to comments on the issue. Because the author of an issue may edit and delete the issue's attachments, a user who opened an issue could rename or delete...
CVE-2026-105268
The Gitea API routes for issue attachments /api/v1/repos/owner/repo/issues/index/assets/attachmentid also accepted attachments that belong to comments on the issue. Because the author of an issue may edit and delete the issue's attachments, a user who opened an issue could rename or delete...
CVE-2026-94278
The File Media Renamer WordPress plugin through 1.3 does not verify that the requesting user is authorised to modify a given media attachment, allowing any user with file-upload privileges to rename attachments belonging to other users, including administrators, and to corrupt unrelated stored si...
CVE-2026-94278 File Media Renamer <= 1.3 - Author+ Arbitrary File Rename via save-attachment-compat
The File Media Renamer WordPress plugin through 1.3 does not verify that the requesting user is authorised to modify a given media attachment, allowing any user with file-upload privileges to rename attachments belonging to other users, including administrators, and to corrupt unrelated stored si...
WordPress File Media Renamer plugin <= 1.3 - Author+ Arbitrary File Rename vulnerability
Author+ Arbitrary File Rename vulnerability discovered by Sebastian Riveros in WordPress Plugin File Media Renamer versions = 1.3...
CVE-2026-94278
The File Media Renamer WordPress plugin (versions
CVE-2026-94278 File Media Renamer <= 1.3 - Author+ Arbitrary File Rename via save-attachment-compat
The File Media Renamer WordPress plugin through 1.3 does not verify that the requesting user is authorised to modify a given media attachment, allowing any user with file-upload privileges to rename attachments belonging to other users, including administrators, and to corrupt unrelated stored si...
EUVD-2026-92968
The File Media Renamer WordPress plugin through 1.3 does not verify that the requesting user is authorised to modify a given media attachment, allowing any user with file-upload privileges to rename attachments belonging to other users, including administrators, and to corrupt unrelated stored si...
CVE-2026-94278: Improper Access Control
The File Media Renamer WordPress plugin through 1.3 does not verify that the requesting user is authorised to modify a given media attachment, allowing any user with file-upload privileges to rename attachments belonging to other users, including administrators, and to corrupt unrelated stored si...
PT-2026-106340
Name of the Vulnerable Software and Affected Versions File Media Renamer versions prior to 1.4 Description The File Media Renamer WordPress plugin fails to verify if the requesting user is authorized to modify a specific media attachment. This allows any user with file-upload privileges to rename...
CVE-2026-105268: Authorization Bypass Through User-Controlled Key
The Gitea API routes for issue attachments /api/v1/repos/owner/repo/issues/index/assets/attachmentid also accepted attachments that belong to comments on the issue. Because the author of an issue may edit and delete the issue's attachments, a user who opened an issue could rename or delete...