# CVE-2024-49325: WordPress Photo Gallery Builder plugin <= 3.0 - Broken Access Control to Notice Dismissal vulnerability

> An attacker can dismiss notices without proper authorization due to missing access controls in the Photo Gallery Builder plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Oct 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-jx6p-33vm-7q3r

## What is CVE-2024-49325?

CVE-2024-49325 is a medium-severity missing authorization vulnerability in wpdiscover Photo Gallery Builder, published on 20 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Missing Authorization vulnerability in wpdiscover Photo Gallery Builder photo-gallery-builder allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Photo Gallery Builder: from n/a through <= 3.0.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Wpdiscover Photo Gallery Builder.

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

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

## Is CVE-2024-49325 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-49325 is a medium-severity missing authorization vulnerability in wpdiscover Photo Gallery Builder, published on 20 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-49325 in the wild and no public exploit code.

Affected product: wpdiscover Photo Gallery Builder. 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-49325/ (Markdown: https://insights.sbomify.com/CVE-2024-49325/index.md)
```

## Sources

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

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