CVE-2024-13751
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 3D Photo Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'des[]' parameter in all versions up to, and including, 1.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 3D Photo Gallery WordPress plugin (versions up to 1.3) is vulnerable to stored Cross-Site Scripting (XSS) via the 'des[]' parameter. Authenticated attackers with Subscriber-level access can inject malicious JavaScript because the plugin fails to sanitize user input and properly escape output when rendering the parameter value.
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.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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 plugin installationLocate the 3D Photo Gallery plugin files in your WordPress plugins directory and confirm the plugin is activeAffected if The plugin is installed and active in WordPress
-
Identify installed versionCheck the plugin header file (typically main php file) for the Version declaration or check via WordPress admin plugins listAffected if The version is 1.3 or lower
-
Check for Subscriber role usersNavigate to Users > All Users in WordPress admin and review user accounts for any with Subscriber role, or query the wp_users and wp_usermeta tables directlyAffected if Any user account has Subscriber-level access or higher
-
Inspect stored des[] parameter dataQuery the WordPress database (typically wp_postmeta table) for meta_key values containing 'des' or the plugin's custom post type meta, or inspect browser developer tools when viewing gallery pages for unsanitized outputAffected if The 'des[]' parameter values are stored and rendered without proper escaping (visible script tags in output)
A user is affected if the 3D Photo Gallery plugin version 1.3 or lower is installed and active with any Subscriber-level user account able to access the vulnerable des[] parameter input.
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 the latest patched version of the plugin. If no patch is available, remove the plugin. For interim mitigation, ensure users do not have Subscriber-level access and implement Web Application Firewall rules to block XSS payloads in the affected parameter.
3D Photo Gallery version 1.4 or later (latest available version)
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the '3D Photo Gallery' plugin
- Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org and upload it
- After updating, verify the plugin is running version 1.4 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13751 — 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-13751 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