CVE-2024-5724
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 Photo Video Gallery Master plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.5.3 via deserialization of untrusted input 'PVGM_all_photos_details' parameter. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.
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 Photo Video Gallery Master WordPress plugin (versions up to 1.5.3) is vulnerable to PHP Object Injection via unsafe deserialization of the 'PVGM_all_photos_details' parameter. Authenticated attackers with Contributor-level access or higher can inject arbitrary PHP objects. While no POP chain exists in the plugin itself, exploitation is possible if another installed plugin/theme provides a usable POP chain for code execution, file operations, or data exfiltration.
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<= 1.5.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.
-
Verify Photo Video Gallery Master plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Photo Video Gallery Master' or 'Webhuntinfotech Photo Video Gallery Master'. Note the displayed version number.Affected if Plugin is installed and version is 1.5.3 or lower
-
Confirm the vulnerable version rangeCompare the installed version against the affected range. The vulnerability affects versions up to and including 1.5.3.Affected if Installed version is 1.5.3 or lower (any version <= 1.5.3)
-
Locate the vulnerable parameter in plugin codeIf you have file access, search the plugin directory for 'PVGM_all_photos_details' - look for code containing unserialize() that processes this parameter. In WordPress, plugins are typically in /wp-content/plugins/photo-video-gallery-master/ or similar.Affected if Code contains unserialize() called on the PVGM_all_photos_details parameter without prior sanitization
-
Check for Contributor-level or higher user accountsIn WordPress admin, go to Users > All Users and review the role assigned to each account. Look for users with Contributor, Author, Editor, or Administrator roles.Affected if Any user account exists with Contributor-level access or higher (these roles can exploit the vulnerability)
-
Review server access logs for exploitation attemptsCheck web server access logs (Apache/Nginx) for requests to any PHP file in the plugin containing 'PVGM_all_photos_details' as a parameter, particularly with serialized data patterns (e.g., O:%, a:%, s:%).Affected if Requests with the PVGM_all_photos_details parameter containing serialized data are present in logs
You are affected if the Photo Video Gallery Master plugin version is 1.5.3 or lower AND you have user accounts with Contributor-level access or higher.
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.
dbcve · scopedUpdate to version 1.5.4 or later. If immediate patching is not feasible, restrict or disable Contributor-level user accounts until the update can be applied.
1.5.4 or latest available version
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Find 'Photo Video Gallery Master' in the plugin list
- Click 'Update Now' if an update is available, or manually update by uploading version 1.5.4 or higher
- Verify the plugin version is 1.5.4 or higher after updating
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5724 — 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-5724 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