Post Layouts for Gutenberg Security & Risk Analysis

wordpress.org/plugins/post-layouts

A beautiful post layouts block to showcase your posts in grid and list layout with multiple templates availability.

2K active installs v1.2.10 PHP 5.6+ WP 4.8+ Updated Apr 22, 2025
grid-layoutlist-layoutpost-blockspost-layoutspost-templates
79
B · Generally Safe
CVEs total1
Unpatched1
Last CVEJul 10, 2024
Safety Verdict

Is Post Layouts for Gutenberg Safe to Use in 2026?

Mostly Safe

Score 79/100

Post Layouts for Gutenberg is generally safe to use. 1 past CVE were resolved. Keep it updated.

1 known CVE 1 unpatched Last CVE: Jul 10, 2024Updated 11mo ago
Risk Assessment

The static analysis of the 'post-layouts' plugin v1.2.10 reveals a generally strong security posture. The absence of identified dangerous functions, file operations, external HTTP requests, and the near-perfect output escaping (98%) are positive indicators. The plugin also demonstrates good practice by using prepared statements for all its SQL queries. However, a significant concern is the complete lack of nonce and capability checks across all potential entry points, including AJAX handlers and REST API routes. While the static analysis reported zero unprotected entry points, this is likely due to the absence of identified handlers and routes, not due to explicit security measures being present.

The plugin has a history of vulnerabilities, most notably a medium-severity Cross-Site Scripting (XSS) vulnerability discovered very recently (July 2024) which remains unpatched. This pattern of a past XSS vulnerability, even if currently patched in newer versions, combined with the current lack of authentication checks on any entry points, suggests a potential for such issues to reappear or be exploited if new entry points are introduced or if the existing ones are indirectly accessible.

In conclusion, while the plugin exhibits good coding practices in areas like SQL handling and output escaping, the absence of critical security checks like nonces and capability checks on all its potential (even if currently zero) entry points is a notable weakness. The recent unpatched XSS vulnerability is a direct red flag, indicating that the plugin is not immune to critical flaws. Users should exercise caution and ensure any available updates patching recent vulnerabilities are applied.

Key Concerns

  • Unpatched CVE present
  • Missing nonce checks on AJAX/REST API
  • Missing capability checks on AJAX/REST API
Vulnerabilities
1

Post Layouts for Gutenberg Security Vulnerabilities

CVEs by Year

1 CVE in 2024 · unpatched
2024
Patched Has unpatched

Severity Breakdown

Medium
1

1 total CVE

CVE-2024-38682medium · 6.4Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Post Layouts for Gutenberg <= 1.2.10 - Authenticated (Contributor+) Stored Cross-Site Scripting

Jul 10, 2024Unpatched
Code Analysis
Analyzed Mar 16, 2026

Post Layouts for Gutenberg Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
1
49 escaped
Nonce Checks
0
Capability Checks
0
File Operations
0
External Requests
0
Bundled Libraries
0

Output Escaping

98% escaped50 total outputs
Attack Surface

Post Layouts for Gutenberg Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 7
actionplugins_loadedpost-layouts.php:41
actioninitpost-layouts.php:50
actionafter_setup_themepost-layouts.php:70
actioninitsrc\blocks\index.php:1126
actionrest_api_initsrc\blocks\index.php:1206
actionwp_headsrc\pl-helper\class-pl-helper.php:75
actionplugins_loadedsrc\pl-helper\class-pl-loader.php:39
Maintenance & Trust

Post Layouts for Gutenberg Maintenance & Trust

Maintenance Signals

WordPress version tested6.8.5
Last updatedApr 22, 2025
PHP min version5.6
Downloads105K

Community Trust

Rating90/100
Number of ratings4
Active installs2K
Developer Profile

Post Layouts for Gutenberg Developer Profile

Alkesh Miyani

2 plugins · 2K total installs

87
trust score
Avg Security Score
90/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect Post Layouts for Gutenberg

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

Asset Paths
/wp-content/plugins/post-layouts/dist/init.js/wp-content/plugins/post-layouts/dist/style.css/wp-content/plugins/post-layouts/admin/assets/admin-menu-settings.css/wp-content/plugins/post-layouts/admin/assets/admin-menu-settings.js/wp-content/plugins/post-layouts/blocks/pl-blog-templates/editor.css/wp-content/plugins/post-layouts/blocks/pl-blog-templates/style.css
Script Paths
/wp-content/plugins/post-layouts/dist/init.js/wp-content/plugins/post-layouts/admin/assets/admin-menu-settings.js
Version Parameters
post-layouts/dist/init.js?ver=post-layouts/dist/style.css?ver=post-layouts/admin/assets/admin-menu-settings.css?ver=post-layouts/admin/assets/admin-menu-settings.js?ver=post-layouts/blocks/pl-blog-templates/editor.css?ver=post-layouts/blocks/pl-blog-templates/style.css?ver=

HTML / DOM Fingerprints

CSS Classes
pl-blocks-wrapperpl-blog-post-gridpl-blog-post-listpl-align-centerpl-align-leftpl-align-rightpl-layout-post-grid-wrapperpl-layout-post-list-wrapper+16 more
HTML Comments
<!-- wp:post-layouts/pl-blog-templates -->
Data Attributes
data-repeat-notice-after
JS Globals
pl
FAQ

Frequently Asked Questions about Post Layouts for Gutenberg