Filtered by vendor Pagelayer
Subscribe
Total
10 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2024-30465 | 1 Pagelayer | 1 Pagelayer | 2024-11-21 | N/A | 6.5 MEDIUM |
| Missing Authorization vulnerability in Pagelayer Team PageLayer.This issue affects PageLayer: from n/a through 1.8.1. | |||||
| CVE-2023-6738 | 1 Pagelayer | 1 Pagelayer | 2024-11-21 | N/A | 5.4 MEDIUM |
| The Page Builder: Pagelayer – Drag and Drop website builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'pagelayer_header_code', 'pagelayer_body_open_code', and 'pagelayer_footer_code' meta fields in all versions up to, and including, 1.7.8 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This appears to be a reintroduction of a vulnerability patched in version 1.7.7. | |||||
| CVE-2023-5124 | 1 Pagelayer | 1 Pagelayer | 2024-11-21 | N/A | 4.8 MEDIUM |
| The Page Builder: Pagelayer WordPress plugin before 1.8.0 doesn't prevent attackers with administrator privileges from inserting malicious JavaScript inside a post's header or footer code, even when unfiltered_html is disallowed, such as in multi-site WordPress configurations. | |||||
| CVE-2023-5087 | 1 Pagelayer | 1 Pagelayer | 2024-11-21 | N/A | 5.4 MEDIUM |
| The Page Builder: Pagelayer WordPress plugin before 1.7.8 doesn't prevent attackers with author privileges and higher from inserting malicious JavaScript inside a post's header or footer code. | |||||
| CVE-2023-4687 | 1 Pagelayer | 1 Pagelayer | 2024-11-21 | N/A | 6.1 MEDIUM |
| The Page Builder: Pagelayer WordPress plugin before 1.7.7 doesn't prevent unauthenticated attackers from updating a post's header or footer code on scheduled posts. | |||||
| CVE-2020-36384 | 1 Pagelayer | 1 Pagelayer | 2024-11-21 | 4.3 MEDIUM | 6.1 MEDIUM |
| PageLayer before 1.3.5 allows reflected XSS via color settings. | |||||
| CVE-2020-36383 | 1 Pagelayer | 1 Pagelayer | 2024-11-21 | 4.3 MEDIUM | 6.1 MEDIUM |
| PageLayer before 1.3.5 allows reflected XSS via the font-size parameter. | |||||
| CVE-2020-35947 | 1 Pagelayer | 1 Pagelayer | 2024-11-21 | 6.5 MEDIUM | 7.4 HIGH |
| An issue was discovered in the PageLayer plugin before 1.1.2 for WordPress. Nearly all of the AJAX action endpoints lacked permission checks, allowing these actions to be executed by anyone authenticated on the site. This happened because nonces were used as a means of authorization, but a nonce was present in a publicly viewable page. The greatest impact was the pagelayer_save_content function that allowed pages to be modified and allowed XSS to occur. | |||||
| CVE-2020-35944 | 1 Pagelayer | 1 Pagelayer | 2024-11-21 | 6.8 MEDIUM | 8.8 HIGH |
| An issue was discovered in the PageLayer plugin before 1.1.2 for WordPress. The pagelayer_settings_page function is vulnerable to CSRF, which can lead to XSS. | |||||
| CVE-2024-43972 | 1 Pagelayer | 1 Pagelayer | 2024-09-25 | N/A | 4.8 MEDIUM |
| Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Pagelayer Team PageLayer allows Stored XSS.This issue affects PageLayer: from n/a through 1.8.7. | |||||