Export limit exceeded: 430457 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (430457 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-132660 | 1 Enterprisedb | 1 Postgres Enterprise Manager | 2026-11-21 | N/A |
| In Postgres Enterprise Manager (PEM), several SECURITY DEFINER functions in the pem schema of the PEM backend database are owned by a superuser but do not set a safe search_path. Any PEM user who can connect to the PEM backend database can create objects that these functions use in place of the intended ones, and so run arbitrary SQL with superuser privileges. Temporary objects can be used for this on every supported PostgreSQL version, and objects in the public schema on PostgreSQL 14 backends and backends upgraded from PostgreSQL 14. From PEM 10.6.1, these functions run with a fixed search_path. | ||||
| CVE-2026-132662 | 1 Enterprisedb | 1 Postgres Enterprise Manager | 2026-11-21 | N/A |
| In Postgres Enterprise Manager (PEM), the SQL Profiler save and load functions in the PEM web application do not keep the client-supplied file name inside the user's storage directory. A user with the SQL Profiler role (pem_comp_sqlprofiler) can read JSON files, and overwrite files that the PEM web server account can write, outside their own storage directory. Overwriting the PEM web application's configuration database stops the web console for all users. From PEM 10.6.1, the SQL Profiler only reads and writes files inside the user's storage directory. | ||||
| CVE-2026-132668 | 1 Enterprisedb | 1 Postgres Enterprise Manager | 2026-11-21 | N/A |
| In Postgres Enterprise Manager (PEM), any PEM user can run the pem.send_webhook() function, which runs with elevated privileges and queues a payload for any configured webhook. The PEM agent then delivers it with that webhook's stored headers, OAuth token or client certificate, so a user can send forged notifications to endpoints they could not otherwise authenticate to. From PEM 10.6.1, no PEM login role can call this function directly. PEM still sends webhook notifications through its own internal paths. | ||||
| CVE-2022-4998 | 1 Kanishka-linux | 1 Reminiscence | 2026-11-21 | 6.3 Medium |
| A vulnerability was identified in kanishka-linux reminiscence 0.3 on Windows. This issue affects the function convert_html_pdf_with_chromium of the file pages/dbaccess.py of the component Chromium HTML-to-PDF Conversion Pipeline. Such manipulation of the argument url_name leads to os command injection. The attack can be launched remotely. The exploit is publicly available and might be used. The project was informed of the problem early through an issue report but has not responded yet. | ||||
| CVE-2026-132920 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 4.3 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4 an SSRF via connection tests was possible for users without project edit permissions | ||||
| CVE-2026-132926 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 4.2 Medium |
| In JetBrains TeamCity before 2026.2 poisoning of OAuth discovery metadata via the X-Forwarded-Host header was possible | ||||
| CVE-2026-132932 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 6.1 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4 reflected XSS in the build log tree view was possible | ||||
| CVE-2026-132935 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 4.3 Medium |
| In JetBrains TeamCity before 2026.2 missing authorization in statistics chart export allowed viewing data of project | ||||
| CVE-2026-132940 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 6.4 Medium |
| In JetBrains TeamCity before 2026.2 credential leakage via Mercurial subrepository URLs was possible | ||||
| CVE-2026-132942 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 5.3 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4 unauthenticated extraction of build parameter values via a timing attack on build status icons was possible | ||||
| CVE-2026-132664 | 1 Enterprisedb | 1 Postgres Enterprise Manager | 2026-11-21 | N/A |
| In Postgres Enterprise Manager (PEM), any PEM user can read the encrypted passwords that PEM agents use to connect to monitored servers, including the PEM backend superuser password stored when the PEM server is configured. Unless a custom encryption key is configured, these passwords are encrypted with a key that is the same in every PEM installation, so they can be decrypted. From PEM 10.6.1, PEM users can no longer read these passwords. | ||||
| CVE-2026-132802 | 1 Ui | 1 Unifi Access Application | 2026-11-21 | 9.9 Critical |
| A malicious actor with access to the network and low privileges could exploit an Improper Link Resolution Before File Access vulnerability found in UniFi Access Application to execute arbitrary code with root privileges on the host device. | ||||
| CVE-2026-132804 | 1 Ui | 1 Unifi Access Application | 2026-11-21 | 9.9 Critical |
| A malicious actor with access to the network and low privileges could exploit a Server-Side Request Forgery (SSRF) vulnerability found in UniFi Access Application to escalate privileges within UniFi OS. | ||||
| CVE-2026-132808 | 1 Ui | 1 Unifi Access Application | 2026-11-21 | 9.9 Critical |
| A malicious actor with access to the network and low privileges could exploit an Incorrect Authorization vulnerability found in UniFi Access Application to execute arbitrary commands on certain adopted UniFi Access devices. | ||||
| CVE-2026-132039 | 1 Eclipse | 1 Eclipse Ditto | 2026-11-21 | N/A |
| In Eclipse Ditto versions before 3.9.9, Thing events delivered via WebSocket, Server-Sent Events and connections disclose field values which the policy does not allow the subscriber to read. A READ revoke for one subject of the subscriber's authorization context is not applied when another of its subjects is granted READ. For subscribers with partial READ access, subscription RQL filters, the SSE `_context`, `thing-json` placeholders and extra fields are evaluated on the unfiltered event. This allows an authenticated subscriber with at least partial READ access to a Thing to obtain the values of fields it may not read when events for that Thing are emitted. | ||||
| CVE-2026-132661 | 1 Enterprisedb | 1 Postgres Enterprise Manager | 2026-11-21 | N/A |
| In Postgres Enterprise Manager (PEM), multi-factor authentication (MFA) is not enforced on the PEM web application's own routes. An attacker who knows the password of a user who has enrolled a second factor can skip the second factor and call PEM's pages and APIs directly, with that user's permissions. A similar issue in pgAdmin 4 was assigned CVE-2024-4215. From PEM 10.6.1, every authenticated PEM route requires a completed MFA check. | ||||
| CVE-2026-132663 | 1 Enterprisedb | 1 Postgres Enterprise Manager | 2026-11-21 | N/A |
| In Postgres Enterprise Manager (PEM), webhook URLs are not validated, and the PEM agent does not restrict the URL schemes it uses to deliver webhooks. A user with the alert configuration role (pem_config_alert) can set up a webhook with a file:// URL. When the webhook is sent, the agent on the PEM server, which runs as root by default, reads the local file and stores its contents in the webhook error record in the PEM database, where any PEM user can read it. From PEM 10.6.1, PEM accepts and sends only http and https webhook URLs. | ||||
| CVE-2026-132665 | 1 Enterprisedb | 1 Postgres Enterprise Manager | 2026-11-21 | N/A |
| In Postgres Enterprise Manager (PEM), the pem.deploy_job_template() function does not check that the caller can access the servers, groups and agents it deploys a job template to. When PEM teams are used to separate access, a user with the scheduled tasks role (pem_manage_schedule_task) can deploy and schedule SQL or shell job steps on agents that belong to other teams. From PEM 10.6.1, PEM checks team access for every server, group and agent a template is deployed to. | ||||
| CVE-2026-126011 | 2 Smub, Wordpress-extensions | 2 Nextgen Gallery, Nextgen Gallery | 2026-11-21 | 7.2 High |
| The Photo Gallery, Sliders, Proofing and Themes – NextGEN Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 4.5.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the site administrator to have configured the Thickbox lightbox effect with the "Try to apply to all images" context (thumbEffectContext=all_images), and exploitation additionally depends on an administrator approving the attacker's initial comment so that subsequent comments from that author are auto-approved. | ||||
| CVE-2026-130150 | 2 Webtoffee, Wordpress-extensions | 2 Product Import Export For Woocommerce, Product Import Export For Woocommerce | 2026-11-21 | 4.7 Medium |
| The Product Import Export for WooCommerce – CSV Product Importer & Exporter plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'author (initial store via wp-comments-post.php) / CSV cell on import' parameter in all versions up to, and including, 2.6.9 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The exploit requires an administrator to approve the attacker's review, then export and re-import it using the plugin's default column mapping, with the import taking the INSERT branch — which occurs automatically on any site whose database table prefix is not the literal 'wp_', when the CSV has no comment_ID mapping, or when the original review has been trashed. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own. | ||||