Export limit exceeded: 430483 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.

Export limit exceeded: 430483 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.

Search

Search Results (430483 CVEs found)

CVE Vendors Products Updated CVSS v3.1
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.
CVE-2026-120486 2 Shortpixel, Wordpress-extensions 2 Shortpixel Image Optimizer, Shortpixel Image Optimizer 2026-11-21 5.4 Medium
The ShortPixel Image Optimizer – Optimize Images, Convert WebP & AVIF plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 6.6.1 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. Exploitation requires the administrator to have enabled the 'Deliver WebP/AVIF images using the ShortPixel CDN' (useCDN) option, after which any unauthenticated visitor can submit a comment containing a crafted url() payload inside an allowed HTML construct such as <acronym title="...">, which WordPress comment kses preserves on save; the dangerous attribute-boundary breakout occurs only at render time inside the ob_start output-buffer rewriter, where kses does not apply.
CVE-2026-122230 2026-11-21 7.2 High
The Thim Kit for Elementor – Pre-built Templates & Widgets for Elementor plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 1.4.8 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. Exploitation requires that the Post Comment widget is used with the Text Reveal entrance animation (Elementor class 'ekit--fx-word-reveal') on a Single Post template, and the comment widget must be within the initial viewport; once the first comment by an attacker is approved, or if comment moderation is disabled, subsequent payloads fire automatically for every visitor who loads the affected page.
CVE-2026-118061 2026-11-21 7.2 High
The VikBooking Hotel Booking Engine & PMS plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'inquiry (array keys)' parameter in all versions up to, and including, 1.8.20 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 endpoint's only access gate is a CSRF token that is publicly emitted on the unauthenticated inquiry page, making the injection reachable by any unauthenticated visitor without any precondition beyond loading that public page.
CVE-2026-119061 2026-11-21 7.2 High
The VikBooking Hotel Booking Engine & PMS plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'vbf<field_id>' parameter in all versions up to, and including, 1.8.20 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.
CVE-2026-107632 2026-11-21 7.2 High
The Unbounce Landing Pages plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 1.1.6. This is due to insufficient input sanitization and output escaping on the proxy error message that is persisted to the 'ub-proxy-error-message' option: unauthenticated attacker-controlled REQUEST_URI data is concatenated into the error string in UBHTTP::stream_request_curl()/stream_request_wp_remote() and stored via update_option(), then later echoed inside a <textarea> on the Unbounce Pages Diagnostics admin page without any escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user (an administrator viewing the Diagnostics screen) accesses an injected page.
CVE-2026-131610 1 Connectwise 1 Automate 2026-11-21 6.5 Medium
In ConnectWise Automate versions prior to 2026.11, a condition in Web Control Center (WCC2) authorization handling could allow an authenticated contact user to access information associated with other clients on the same Automate server through API requests. This may result in disclosure of information outside the user’s assigned access scope. The issue is limited to information disclosure and does not extend existing modification or command execution permissions. This issue is resolved in ConnectWise Automate 2026.11.
CVE-2026-131180 1 Splunk 1 Splunk Enterprise 2026-11-21 6.3 Medium
In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role could create and share a dashboard that contains attacker-controlled Search Processing Language (SPL). The SPL could run using the permissions of the user who opens the dashboard. With this access, the user who created the dashboard could expose stored credentials and write data to an index. The vulnerability is possible because Splunk Enterprise does not correctly escape field names in searches that use the rename command. For more information see rename (https://help.splunk.com/en/splunk-enterprise/spl-search-reference/10.4/search-commands/rename) and SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands) in the Splunk documentation.
CVE-2026-131182 1 Splunk 1 Splunk Enterprise 2026-11-21 7.6 High
In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role could store malicious Search Processing Language (SPL) in a shared dashboard. The malicious SPL could run using the permissions of the user who opened the dashboard and could access or modify data available to that user and disrupt Splunk Enterprise availability. The vulnerability is possible because Splunk Enterprise does not preserve quoted search argument boundaries when it processes a dashboard search. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The attacker, a user who holds the "power" Splunk role, should not be able to exploit the vulnerability at will.
CVE-2026-131185 1 Splunk 1 Splunk Enterprise 2026-11-21 6.5 Medium
In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who does not hold the "admin" or "power" Splunk roles could use the apps backup and restore Representational State Transfer (REST) API to prevent subsequent apps backup or restore operations until Splunk Enterprise restarts. This could result in a Denial of Service (DoS). The vulnerability is possible because the apps backup and restore REST API handlers do not correctly enforce authorization.
CVE-2026-131187 1 Splunk 1 Splunk Enterprise 2026-11-21 4.3 Medium
In Splunk Enterprise versions below 10.6.1, 10.4.5, and 10.2.9, a low-privileged user who does not hold the "admin" or "power" Splunk roles could access file path and metadata listings from search head knowledge bundles via the Representational State Transfer (REST) API. This unauthorized access could expose sensitive metadata, including Splunk platform usernames, private knowledge-object configuration file names, installed application directories, and the file path names of security-sensitive configuration and key files. The vulnerability is possible because the REST API actions that list bundle contents and denied files use a capability available to the "user" role instead of requiring distributed-search administration capabilities. For more information see Knowledge bundle replication overview (https://help.splunk.com/en/splunk-enterprise/administer/distributed-search/10.6/knowledge-bundle-replication/knowledge-bundle-replication-overview) in the Splunk documentation. For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.
CVE-2026-131195 1 Splunk 1 Splunk Enterprise 2026-11-21 5.9 Medium
In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could send repeated HTTP PubSub channel subscription requests that cause a Denial of Service (DoS) by permanently increasing memory usage until Splunk Enterprise exhausts available memory. The vulnerability affects instances that turn on the [pubsubsvr-http] stanza in server.conf because the HTTP PubSub broker does not release memory associated with a channel after the client disconnects.
CVE-2026-131220 1 Splunk 1 Enterprise Security 2026-11-21 5.9 Medium
In Splunk Enterprise Security versions below 8.7.0, a user who can influence event values that populate an affected data model based on the Common Information Model could cause attacker-controlled values to appear in an affected Dashboard Studio view. Another authenticated user could later click a corresponding row in that view. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who clicked the row. The commands could access or modify some data available to the user who clicked the row. The vulnerability is possible because affected Dashboard Studio drilldowns do not safely quote data model values before including them in searches. For more information see Users and roles for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/users-and-roles-for-splunk-enterprise-security) and Create a dashboard in Dashboard Studio (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/dashboard-studio/10.2/create-a-dashboard-in-dashboard-studio/create-a-dashboard-in-dashboard-studio) in the Splunk documentation.
CVE-2026-131237 1 Splunk 1 Enterprise Security 2026-11-21 5.4 Medium
In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in data used by the Weak Encrypted Communication report. If another user who can access the report selects an affected drilldown, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the drilldown. The user who stores the values could then access sensitive data and modify some data available to the user who selects the drilldown. The vulnerability is possible because the Weak Encrypted Communication report does not validate source, destination, and Secure Sockets Layer version values before inserting them into drilldown searches. For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) and Weak Encrypted Communication (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-reports/weak-encrypted-communication) in the Splunk documentation.
CVE-2026-131868 2026-11-21 7.5 High
Convert::ASN1 versions before 0.37 for Perl allow memory exhaustion via a declared element length passed unchecked to sysread in asn_read and asn_get. The length an element declares in its BER header is passed to sysread as the read size. Perl grows the target buffer to that size before reading, so memory is allocated from the declared length, not from the data received. A 6-byte header can declare a length of up to 4GB. A single header makes the reading process allocate the declared size. Where the allocation fails, perl exits with "Out of memory", which eval cannot catch.
CVE-2026-132600 2 Getwpfunnels, Wordpress-extensions 2 Mail Mint, Mail Mint 2026-11-21 6.4 Medium
The Mail Mint – Email Marketing, Automation & WooCommerce Emails with AI Assistance plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'form_id' parameter in all versions up to, and including, 1.31.9 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. A crafted form_id value such as `1" onmouseover="alert(1)` still resolves to a valid form ID via FormModel::get()'s %d prepared statement placeholder, allowing the payload to bypass empty/draft early-return guards and reach both the HTML id and hidden input value attribute sinks.
CVE-2026-131733 2 Brainstormforce, Wordpress-extensions 2 Surecart, Surecart 2026-11-21 5.3 Medium
Missing Authorization vulnerability in Brainstorm Force SureCart surecart allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects SureCart: from n/a through 4.13.0.