Wp Blog Post LayoutsWordPress extension · Codevibrant
CVE-2024-5503
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe WP Blog Post Layouts plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.1.3. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary PHP files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe WP Blog Post Layouts WordPress plugin (versions up to 1.1.3) contains a local file inclusion vulnerability that allows authenticated attackers with Contributor-level access or higher to include and execute arbitrary PHP files on the server, enabling code execution and potential bypass of access controls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Wp Blog Post LayoutsWordPress extension
<= 1.1.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if the WP Blog Post Layouts plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP Blog Post Layouts' by Codevibrant. Alternatively, check the /wp-content/plugins/ directory for a folder named 'cv-wp-blog-post-layouts' or similar Codevibrant plugin folder.Affected if The plugin is present in the WordPress installation.
-
Determine the installed plugin versionIn the WordPress plugin list, click on the plugin name to view details, or open the main plugin PHP file (usually named index.php or similar) in /wp-content/plugins/ and look for the 'Version' header in the plugin comment block.Affected if The version number displayed is 1.1.3 or lower.
-
Check for user accounts with Contributor-level or higher accessIn WordPress admin, go to Users > All Users and review the 'Role' column. Look for any accounts assigned Contributor, Author, Editor, or Administrator roles.Affected if There is at least one user account with Contributor, Author, Editor, or Administrator role.
-
Inspect for suspicious PHP files in upload directoriesCheck the /wp-content/uploads/ directory (and subdirectories) for any recently created .php files, especially those with randomized names or located in unexpected folders. Use file system commands or FTP to list recently modified files.Affected if Unexpected or recently created PHP files are found in upload directories.
-
Review access logs for file inclusion requestsExamine web server access logs (Apache, Nginx) for requests to the plugin that include '?file=' or similar parameters pointing to PHP files, or requests with directory traversal patterns (e.g., ../../).
You are affected if the WP Blog Post Layouts plugin is installed at version 1.1.3 or lower AND your site has at least one user with Contributor-level or higher access.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the plugin to version 1.1.4 or later immediately. If an update is unavailable, remove the plugin. Audit user accounts with Contributor-level or higher access and check for any recently uploaded malicious files.
Fix this in Wp Blog Post Layouts
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5503 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-5503 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data