CVE-2024-1487
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 Photos and Files Contest Gallery WordPress plugin before 21.3.1 does not sanitize and escape some parameters, which could allow users with a role as low as author to perform Cross-Site Scripting attacks.
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 · moderate confidenceThe Photos and Files Contest Gallery WordPress plugin before version 21.3.1 fails to properly sanitize and escape certain input parameters, enabling authenticated Cross-Site Scripting (XSS) attacks. Users with author-level permissions or higher can inject malicious scripts that execute in the browsers of other users viewing the affected plugin pages.
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< 21.3.1CVSS 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.
-
Check the installed Contest Gallery plugin versionIn WordPress admin, go to Plugins > Installed Plugins, locate 'Contest Gallery Photos and Files' and read the version number displayed under the plugin name. Alternatively, check the plugin's main PHP file header or the readme.txt file for the 'Version' field.Affected if The version number is lower than 21.3.1 (e.g., 21.3.0, 21.2.x, etc.)
-
Verify the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and confirm that Contest Gallery is currently activated. Also check if any contest galleries have been created by visiting the plugin's admin pages.Affected if The plugin is active and running a version below 21.3.1
-
Confirm presence of users with author-level or higher privilegesIn WordPress admin, go to Users > All Users and review the role column. Check if any users have the 'Author', 'Editor', or 'Administrator' role assigned.Affected if There are users with author-level permissions or higher, as these roles can trigger the vulnerable code paths
-
Identify access to plugin admin pagesIn WordPress admin, navigate to the Contest Gallery menu items (typically found under a 'Contest Gallery' top-level menu). Access the gallery management or contest creation pages where user input is handled.Affected if You can access plugin pages and the installed version is below 21.3.1 - the XSS payload would execute when viewing galleries or contest pages
You are affected if the Contest Gallery plugin version is below 21.3.1, the plugin is active, and you have users with author-level or higher permissions who can access the plugin's input fields.
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 · scoped21.3.1
Update the Photos and Files Contest Gallery plugin to version 21.3.1 or later, which includes proper input sanitization and output escaping for the affected parameters.
Contest Gallery version 21.3.1 or later
- Back up your WordPress site and database before making any changes
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Find the Contest Gallery plugin in the list
- Click Update Now if an update is available, or manually upload version 21.3.1 or later from the WordPress plugin repository
- Verify the plugin version shows 21.3.1 or higher after updating
- Clear any caching plugins or server-side caches
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-1487 — 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-1487 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