Search

Search Results (430483 CVEs found)

CVE Vendors Products Updated CVSS v3.1
CVE-2026-132658 1 Enterprisedb 1 Postgres Enterprise Manager 2026-11-21 N/A
In Postgres Enterprise Manager (PEM), the pem_agent role, which every PEM agent login inherits, is a member of the PostgreSQL pg_read_server_files and pg_write_server_files roles on the PEM backend database. An attacker who controls any monitored host, and so its PEM agent certificate, can read and write files on the PEM server host as the postgres operating system user. This includes the PEM certificate authority key, which lets the attacker issue certificates for other agents and act as them. From PEM 10.6.1, PEM agents no longer hold these roles.
CVE-2026-133964 1 Bytebase 1 Dbhub 2026-11-21 6.3 Medium
A security vulnerability has been detected in Bytebase DBHub up to 2.0.0. Impacted is the function escapeHatchFunctionKeywords of the file src/utils/allowed-keywords.ts of the component Read Only Mode. The manipulation of the argument tool leads to incomplete blacklist. Remote exploitation of the attack is possible. The vendor was contacted early about this disclosure but did not respond in any way.
CVE-2026-131197 1 Splunk 1 Splunk Enterprise 2026-11-21 6.4 Medium
In Splunk Enterprise versions below 10.4.5, 10.2.9, and 10.0.12, a low-privileged user who holds the "power" Splunk role could overwrite shared application dashboard views with arbitrary Search Processing Language (SPL) commands. When another authenticated user opens an affected dashboard in Splunk Web, Splunk Enterprise executes the injected SPL using the viewing user's permissions, potentially allowing the low-privileged user to access or modify data available to that user. The vulnerability is possible because the affected app grants the "power" Splunk role write access to shared dashboard views that should be writable only by the "admin" Splunk role. The vulnerability is possible because the Splunk App for Splunk Observability Cloud grants the "power" Splunk role write access to shared dashboard views that should be writable only by the "admin" Splunk role
CVE-2026-131205 1 Splunk 1 Enterprise Security 2026-11-21 5.4 Medium
In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_user" Splunk Enterprise Security role could store attacker-controlled asset data in an asset source lookup. A user that holds a role with the mc_assets_read capability could later open the Asset Center dashboard and select that value in the Asset Information table. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of that user. With this access, the user who stored the asset data could expose or modify data available to the user who selected the value. The vulnerability is possible because Asset Center does not escape asset values before adding them to drilldown searches. The vulnerability requires Asset Center to process the asset data and another user to select the value. The user who stored the data should not be able to exploit the vulnerability at will. 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), Add asset and identity data to Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.7/asset-and-identity-management/add-asset-and-identity-data-to-splunk-enterprise-security), and Asset and identity dashboards (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/analytics/asset-and-identity-dashboards) in the Splunk documentation.
CVE-2026-131207 1 Splunk 1 Enterprise Security 2026-11-21 5.4 Medium
In Splunk Enterprise Security versions below 8.7.0, an authenticated user who does not hold the edit_correlationsearches capability could set Status to Testing for a versioned detection or clear that setting. This could affect the integrity and availability of detection testing. The vulnerability is possible because the Test Mode Representational State Transfer (REST) API does not require the edit_correlationsearches capability before it creates or deletes scheduled test copies of detections. For more information see Capability reference for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/capability-reference-for-splunk-enterprise-security) and Test detections on production data using Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.7/detections/test-detections-on-production-data-using-splunk-enterprise-security) in the Splunk documentation.
CVE-2026-131211 1 Splunk 1 Enterprise Security 2026-11-21 7.3 High
In Splunk App for Payment Card Industry Compliance versions below 8.7.0, a user who holds the "ess_user" Splunk Enterprise Security role could add attacker-controlled values to lookup data used by the Primary Functions report. If another authenticated user later selects the value in the Primary Function Summary panel, the Splunk App for Payment Card Industry Compliance could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selected the value. With this access, the first user could expose or modify data available to the user who selected the value. The vulnerability is possible because the Primary Functions report does not safely escape report values before including them in drilldown 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 Reports (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/user-manual/8.7/using-the-splunk-app-for-pci-compliance/reports) in the Splunk documentation.
CVE-2026-131216 1 Splunk 1 Enterprise Security 2026-11-21 5.7 Medium
In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the manage_all_investigations capability could store attacker-controlled script content in a legacy investigation workbench panel title. Another authenticated user could later open a legacy investigation workbench that renders the panel. The script could then run in the browser of the user who opened the workbench and expose data or actions available through Splunk Web to the user who opened the workbench. The vulnerability is possible because Splunk Enterprise Security does not escape legacy investigation workbench panel titles before rendering them in Splunk Web. For more information see Capability reference for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/capability-reference-for-splunk-enterprise-security) and Review and finish existing legacy investigations in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.4/investigations/review-and-finish-existing-legacy-investigations-in-splunk-enterprise-security) in the Splunk documentation.
CVE-2026-131217 1 Splunk 1 Enterprise Security 2026-11-21 4.6 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 that populates the System Misconfigurations report. Another user with access to the report could later select a related row. The System Misconfigurations report could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selected the row. The commands could access or modify data available to the user who selected the row. The vulnerability is possible because the System Misconfigurations report does not treat values from the Vulnerabilities data model as literal search values when it builds drilldown searches. For more information see System Misconfigurations (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-reports/system-misconfigurations) and Configure users and roles (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-the-app/configure-users-and-roles) in the Splunk documentation.
CVE-2026-131221 1 Splunk 1 Enterprise Security 2026-11-21 4.6 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 intrusion detection data. Another user who holds the "pci_user" role could later select the corresponding row in the Intrusion Detection and Prevention System Alert Activity Details panel. The report could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selected the row. The commands could access data and perform actions available to the user who selected the row. The vulnerability is possible because the Intrusion Detection and Prevention System Alert Activity report does not treat intrusion detection values as literal search values when it builds the details drilldown search. For more information see Reports (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/user-manual/8.7/using-the-splunk-app-for-pci-compliance/reports) and Configure users and roles (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-the-app/configure-users-and-roles) in the Splunk documentation.
CVE-2026-131763 2 Nsquared, Wordpress-extensions 2 Simply Schedule Appointments, Simply Schedule Appointments 2026-11-21 5.4 Medium
Missing Authorization vulnerability in NSquared Simply Schedule Appointments simply-schedule-appointments allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Simply Schedule Appointments: from n/a through 1.6.13.6.
CVE-2026-131580 2 Posimyththemes, Wordpress-extensions 2 Uichemy – Convert Figma, Prompts And Ai Builds To Elementor, Gutenberg And Bricks, Uichemy 2026-11-21 4.4 Medium
The UiChemy – Convert Figma, Prompts and AI Builds to Elementor, Gutenberg and Bricks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'head' parameter in all versions up to, and including, 5.6.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with editor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. On a default single-site WordPress installation, Editors hold the 'unfiltered_html' capability, meaning the plugin's only effective gate passes for Editor-level users, and the secondary UiChemy_Roles check is a no-op on the Free build and default Pro configuration.
CVE-2026-131740 2 Wordpress-extensions, Wp Royal 2 Royal Elementor Addons, Royal Elementor Addons 2026-11-21 6.5 Medium
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WProyal Royal Elementor Addons royal-elementor-addons allows Stored XSS.This issue affects Royal Elementor Addons: from n/a through 1.7.1069.
CVE-2026-131712 2 Wordpress-extensions, Wpmet 2 Shopengine, Shopengine 2026-11-21 5.3 Medium
Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in Wpmet ShopEngine shopengine allows Code Injection.This issue affects ShopEngine: from n/a through 4.9.9.
CVE-2026-131711 2026-11-21 5.3 Medium
Missing Authorization vulnerability in ThemeGrill Masteriyo - LMS learning-management-system allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Masteriyo - LMS: from n/a through 3.5.1.
CVE-2026-131770 2 Liquid Web / Stellarwp, Wordpress-extensions 2 The Events Calendar, The Events Calendar 2026-11-21 4.3 Medium
Missing Authorization vulnerability in Liquid Web / StellarWP The Events Calendar the-events-calendar allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects The Events Calendar: from n/a through 6.18.4.
CVE-2026-131723 2 Liquid Web / Stellarwp, Wordpress-extensions 2 Event Tickets, Event Tickets 2026-11-21 5.3 Medium
Missing Authorization vulnerability in Liquid Web / StellarWP Event Tickets event-tickets allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Event Tickets: from n/a through 5.31.1.
CVE-2026-131757 2 Wordpress-extensions, Wp Royal 2 Royal Elementor Addons, Royal Elementor Addons 2026-11-21 5.3 Medium
Insertion of Sensitive Information Into Sent Data vulnerability in WProyal Royal Elementor Addons royal-elementor-addons allows Retrieve Embedded Sensitive Data.This issue affects Royal Elementor Addons: from n/a through 1.7.1069.
CVE-2026-131727 2 Blubrry Podcasting, Wordpress-extensions 2 Powerpress Podcasting, Powerpress Podcasting 2026-11-21 6.5 Medium
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Blubrry Podcasting PowerPress Podcasting powerpress allows Stored XSS.This issue affects PowerPress Podcasting: from n/a through 11.18.4.
CVE-2026-131766 2026-11-21 5.3 Medium
Missing Authorization vulnerability in LeapWorx Premium Addons for Elementor premium-addons-for-elementor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Premium Addons for Elementor: from n/a through 4.11.119.
CVE-2026-131751 2026-11-21 5.3 Medium
Missing Authorization vulnerability in Magepeople inc. WpEvently mage-eventpress allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WpEvently: from n/a through 5.7.13.