4 results (0.039 seconds)

CVSS: 5.5EPSS: 0%CPEs: 1EXPL: 1

The WP Page Builder WordPress plugin through 1.2.8 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup). El complemento de WordPress WP Page Builder hasta la versión 1.2.8 no sanitiza ni escapa a algunas de sus configuraciones, lo que podría permitir a usuarios con privilegios elevados, como el administrador, realizar ataques de cross site scripting almacenado incluso cuando la capacidad unfiltered_html no está permitida (por ejemplo, en la configuración de múltiples sitios). The WP Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via plugin settings in versions up to, and including, 1.2.8 due to insufficient input sanitization and output escaping. This makes it possible for administrator-level attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. • https://wpscan.com/vulnerability/98b2321d-fb66-4e02-9906-63af7b08d647 • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •

CVSS: 6.4EPSS: 0%CPEs: 1EXPL: 0

Multiple Auth. (author+) Stored Cross-Site Scripting (XSS) vulnerabilities in WP Page Builder plugin <= 1.2.6 on WordPress. Multiples vulnerabilidades de Cross-Site Scripting (XSS) Almacenado autenticado (con permisos de autor o superiores) en el complemento WP Page Builder en versiones &lt;= 1.2.6 en WordPress. The WP Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via several parameters in versions up to, and including, 1.2.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. • https://patchstack.com/database/vulnerability/wp-pagebuilder/wordpress-wp-page-builder-plugin-1-2-6-multiple-auth-stored-cross-site-scripting-xss-vulnerabilities?_s_id=cve https://wordpress.org/plugins/wp-pagebuilder • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •

CVSS: 5.4EPSS: 0%CPEs: 1EXPL: 1

By default, the WP Page Builder WordPress plugin before 1.2.4 allows subscriber-level users to edit and make changes to any and all posts pages - user roles must be specifically blocked from editing posts and pages. Por defecto, el plugin de WordPress WP Page Builder versiones anteriores a 1.2.4, permite a usuarios de nivel de suscriptor editar y realizar cambios en todas y cada una de las páginas de publicaciones; los roles de usuario deben ser bloqueados específicamente para que no puedan editar publicaciones y páginas • https://wpscan.com/vulnerability/21e7a46f-e9a3-4b20-b44a-a5b6ce7b7ce6 https://www.themeum.com/wp-page-builder-updated-v1-2-4 • CWE-269: Improper Privilege Management CWE-863: Incorrect Authorization CWE-1188: Initialization of a Resource with an Insecure Default •

CVSS: 7.4EPSS: 0%CPEs: 1EXPL: 1

The editor of the WP Page Builder WordPress plugin before 1.2.4 allows lower-privileged users to insert unfiltered HTML, including JavaScript, into pages via the “Raw HTML” widget and the “Custom HTML” widgets (though the custom HTML widget requires sending a crafted request - it appears that this widget uses some form of client side validation but not server side validation), all of which are added via the “page_builder_data” parameter when performing the “wppb_page_save” AJAX action. It is also possible to insert malicious JavaScript via the “wppb_page_css” parameter (this can be done by closing out the style tag and opening a script tag) when performing the “wppb_page_save” AJAX action. El editor del plugin de WordPress WP Page Builder versiones anteriores a 1.2.4, permite a usuarios menos privilegiados insertar HTML sin filtrar, incluido JavaScript, en las páginas por medio del widget "Raw HTML" y los widgets "Custom HTML" (aunque el widget HTML personalizado requiere el envío una petición diseñada (parece que este widget utiliza alguna forma de comprobación del lado del cliente pero no del lado del servidor), todos los cuales son agregados por medio del parámetro "page_builder_data" al realizar la acción AJAX "wppb_page_save".&#xa0;También es posible insertar JavaScript malicioso por medio del parámetro "wppb_page_css" (esto puede ser realizado al cerrar la etiqueta de estilo y abriendo una etiqueta de script) cuando se lleva a cabo la acción AJAX "wppb_page_save" • https://wpscan.com/vulnerability/c20e243d-b0de-4ae5-9a0d-b9d02c9b8141 https://www.themeum.com/wp-page-builder-updated-v1-2-4 • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •