EUVD-2026-125237

NocoDB from 2026.05.2 before 2026.07.0 contains a server-side request forgery vulnerability that allows Editor-role users to fetch internal URLs because data import reused the webhook internal-network exemption. When NCALLOWLOCALHOOKS or NCWEBHOOKALLOWPRIVATENETWORK is set, attackers can request...

CVE-2026-126284

NocoDB versions 2026.05.2 before 2026.07.0 are vulnerable to a Server-Side Request Forgery (SSRF) . The root cause is that the data import functionality incorrectly reused the webhook internal-network exemption. When the configurations NC_ALLOW_LOCAL_HOOKS or NC_WEBHOOK_ALLOW_PRIVATE_NETWORK are ...

CVE-2026-125711

The Widgets for Google Reviews WordPress plugin before 14.3, WP Tripadvisor Review Widgets WordPress plugin before 14.3, Widgets for Booking.com Reviews WordPress plugin before 14.3, Widgets for Reviews & Recommendations WordPress plugin before 14.3, Widgets for Airbnb Reviews WordPress plugin...

CVE-2026-120407

The Contact Form 7 WordPress plugin before 6.2.5 does not restrict which user properties a form field's default value can be populated from, allowing users with the Editor role and above to obtain the password hash and sensitive user meta such as two-factor secrets of higher-privileged users,...

CVE-2026-125711

Multiple Trustindex Review Widget plugins for WordPress (including Google, Tripadvisor, Booking.com, Airbnb, Yelp, and others) before version 14.3 are vulnerable to Stored Cross-Site Scripting (XSS) . The root cause is the failure to properly sanitise and escape connected business details before ...

EUVD-2026-124852

The Widgets for Google Reviews WordPress plugin before 14.3, WP Tripadvisor Review Widgets WordPress plugin before 14.3, Widgets for Booking.com Reviews WordPress plugin before 14.3, Widgets for Reviews & Recommendations WordPress plugin before 14.3, Widgets for Airbnb Reviews WordPress plugin...

CVE-2026-120407

The Contact Form 7 WordPress plugin (versions before 6.2.5 ) contains a vulnerability where form field default values do not restrict which user properties they can be populated from. This flaw allows users with the Editor role or higher to access sensitive information, such as password hashes an...

EUVD-2026-124841

The Contact Form 7 WordPress plugin before 6.2.5 does not restrict which user properties a form field's default value can be populated from, allowing users with the Editor role and above to obtain the password hash and sensitive user meta such as two-factor secrets of higher-privileged users,...

Welcart e-Commerce < 2.11.32 - SQL Injection

Welcart e-Commerce WordPress plugin 2.11.32 contains a SQL injection caused by improper sanitization of values from imported CSV files, letting users with Editor role and above execute arbitrary SQL commands, exploit requires Editor or higher privileges. id: CVE-2026-16065 info: name: Welcart...

CVE-2026-14242

A user with the Editor role could delete, move, push or pull Git Sync managed resources in folders where they only had view access, by creating a provisioning job through the jobs resource API, which skipped the folder permission checks incorrect authorization...

CVE-2026-111000

A user with the Editor role who can edit a folder can move it, through the folders resource API, under a folder they administer, and so gain Admin on the moved folder and its contents, including the right to change their permissions. The legacy folder move API refuses the same move improper...

CVE-2026-111024

A user with the Viewer or Editor role could bypass folder permissions on Git Sync managed resources through the repository files API: a Viewer could read files in folders they could not access, and an Editor could create, modify, move or delete provisioned dashboards and folders there incorrect...

CVE-2026-111000 Privilege escalation through folder move in the folders API

A user with the Editor role who can edit a folder can move it, through the folders resource API, under a folder they administer, and so gain Admin on the moved folder and its contents, including the right to change their permissions. The legacy folder move API refuses the same move improper...

CVE-2026-111000

A user with the Editor role who can edit a folder can move it, through the folders resource API, under a folder they administer, and so gain Admin on the moved folder and its contents, including the right to change their permissions. The legacy folder move API refuses the same move improper...

CVE-2026-111000

A privilege escalation vulnerability exists in the folders resource API where a user with the Editor role can move a folder they have permission to edit into a folder they already administer. This action allows the user to gain Admin rights over the moved folder and its contents, including the ab...

EUVD-2026-123537

A user with the Editor role could delete, move, push or pull Git Sync managed resources in folders where they only had view access, by creating a provisioning job through the jobs resource API, which skipped the folder permission checks incorrect authorization...

CVE-2026-14242

A user with the Editor role could delete, move, push or pull Git Sync managed resources in folders where they only had view access, by creating a provisioning job through the jobs resource API, which skipped the folder permission checks incorrect authorization...

CVE-2026-14242 Authorization bypass in the Git Sync provisioning jobs API

A user with the Editor role could delete, move, push or pull Git Sync managed resources in folders where they only had view access, by creating a provisioning job through the jobs resource API, which skipped the folder permission checks incorrect authorization...

CVE-2026-14242

A user with the Editor role can perform unauthorized actions, such as deleting, moving, pushing, or pulling Git Sync managed resources , in folders where they only have view access. This is due to an incorrect authorization flaw in the jobs resource API , which fails to perform necessary folder p...

PT-2026-145248

A user with the Editor role who can edit a folder can move it, through the folders resource API, under a folder they administer, and so gain Admin on the moved folder and its contents, including the right to change their permissions. The legacy folder move API refuses the same move improper...