EUVD-2026-47927
GHSA-8w85-6hx8-qc3f
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
PR:L reflects mandatory Contributor authentication; UI:R corrects the NVD vector because an administrator must visit a specifically crafted admin URL to trigger payload execution.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
Lifecycle Timeline
2DescriptionCVE.org
The Lpagery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via post titles in versions up to, and including, 2.5.7. This is due to insufficient input sanitization and output escaping in the lpagery_add_filter_text_template_post() function, which is hooked to admin_footer and echoes the raw post_title of the post referenced by the ?lpagery_template query parameter directly inside a JavaScript single-quoted string literal, without esc_js(), esc_html(), or any other encoding. 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 higher-privileged user (such as an administrator) accesses an admin page with the ?lpagery_template=<post_id> parameter pointing at the attacker's post.
AnalysisAI
Stored cross-site scripting in the Lpagery (Bulk Page Generator) WordPress plugin, versions up to and including 2.5.7, allows authenticated attackers with Contributor-level access to inject arbitrary JavaScript via crafted post titles. The vulnerability stems from the lpagery_add_filter_text_template_post() function echoing a raw post_title directly into an inline JavaScript single-quoted string literal on every admin page load, with no encoding applied. When an administrator accesses an admin page bearing the ?lpagery_template parameter pointing to the attacker's post, the injected payload executes in the admin's browser context, enabling session hijacking or unauthorized privileged actions. No public exploit code or CISA KEV listing has been identified at time of analysis.
Technical ContextAI
The flaw lives in the lpagery_add_filter_text_template_post() function within lpagery.php (lines 502-513 of the 2.5.7 tagged release, confirmed via WordPress.org Trac references). This function is registered as a WordPress admin_footer action hook, causing it to fire on every admin page load. When the ?lpagery_template GET parameter is present, the function queries the database for the corresponding post_title and interpolates that value directly into an inline JavaScript single-quoted string literal - without applying WordPress-native encoding functions such as esc_js(), esc_html(), or wp_json_encode(). An attacker-controlled title containing a single quote and JavaScript syntax can break out of the string context and inject executable code. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation - Cross-site Scripting) in its stored/persistent variant, because the payload is persisted in the post_title database field before rendering. The affected product is identified in CPE as cpe:2.3:a:niklaslindemann:bulk_page_generator_-_lpagery:*:*:*:*:*:*:*:*.
RemediationAI
Update the Lpagery plugin to a version beyond 2.5.7; a code fix is confirmed delivered via WordPress.org plugin repository changeset 3611156 (https://plugins.trac.wordpress.org/changeset?reponame=&old=3611156%40lpagery&new=3611156%40lpagery), which should correspond to a release above 2.5.7 - verify the exact patched version number through the WordPress.org plugin page or the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/6720e68e-16fc-48c2-ad56-1f44a3e78bb2. Where an immediate update is not feasible, restrict Contributor-role users from creating or editing posts on sites running this plugin, which eliminates the ability to plant the payload at the cost of editorial workflow disruption. As a partial WAF-level control, block admin requests containing the ?lpagery_template parameter from sessions without Administrator-level authentication; this limits exposure but is bypassable and does not address the root encoding defect. Disabling the plugin entirely until patching is complete is the safest interim option with no security trade-offs beyond loss of the plugin's functionality.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
Same weakness CWE-79 – Cross-site Scripting (XSS)
View allShare
External POC / Exploit Code
Leaving vuln.today