# CVE-2024-11642: Post Grid Master <= 3.4.12 - Missing Authorization to Unauthenticated Local PHP File Inclusion

> Unauthenticated attackers can exploit a local file inclusion vulnerability in the Post Grid Master WordPress plugin to execute arbitrary PHP code and read sensitive data.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-7pmr-9fj2-66gq

## What is CVE-2024-11642?

CVE-2024-11642 is a critical path traversal vulnerability in mdshuvo Post Grid Master — Post Grids & AJAX Filters, published on 9 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Post Grid Master – Custom Post Types, Taxonomies & Ajax Filter Everything with Infinite Scroll, Load More, Pagination & Shortcode Builder plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 3.4.12 via the 'locate_template' function. This makes it possible for unauthenticated attackers to include and execute arbitrary 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. The file included must have a .php extension.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2024-11642?

It affects 1 product.


Products: Addonmaster Post Grid Master.

## How do I fix CVE-2024-11642?

No fix has been published for CVE-2024-11642 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-11642 being exploited?

There is no known exploitation of CVE-2024-11642 in the wild and no public exploit code.

## Other vulnerabilities in mdshuvo Post Grid Master — Post Grids & AJAX Filters

- [CVE-2024-43156](https://insights.sbomify.com/CVE-2024-43156/): WordPress Post Grid Master plugin <= 3.4.10 - Reflected Cross Site Scripting (XSS) vulnerability (high 7.1)
- [CVE-2025-24733](https://insights.sbomify.com/CVE-2025-24733/): WordPress Post Grid Master plugin <= 3.4.12 - Local File Inclusion vulnerability (medium 6.5)
- [CVE-2024-34390](https://insights.sbomify.com/CVE-2024-34390/): WordPress Post Grid Master plugin <= 3.4.8 - Auth. Cross Site Scripting (XSS) vulnerability (medium 6.5)
- [CVE-2025-5084](https://insights.sbomify.com/CVE-2025-5084/): Post Grid Master <= 3.4.13 - Reflected Cross-Site Scripting via argsArray['read_more_text'] (medium 6.1)
- [CVE-2024-34372](https://insights.sbomify.com/CVE-2024-34372/): WordPress Post Grid Master plugin <= 3.4.7 - Broken Access Control vulnerability (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-11642 and fix it if it is affected.

What it is: CVE-2024-11642 is a critical path traversal vulnerability in mdshuvo Post Grid Master — Post Grids & AJAX Filters, published on 9 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-11642 in the wild and no public exploit code.

Affected product: mdshuvo Post Grid Master — Post Grids & AJAX Filters. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-11642/ (Markdown: https://insights.sbomify.com/CVE-2024-11642/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-11642
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-11642
- OSV: https://osv.dev/vulnerability/CVE-2024-11642

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-11642/
Summaries are generated and may contain mistakes; the official description above is the record.