Wp Easy Post TypesWordPress extension · Newsignature
CVE-2024-10080
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 WP Easy Post Types plugin for WordPress is vulnerable to Stored Cross-Site Scripting via post meta in versions up to, and including, 1.4.4 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions 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 WP Easy Post Types WordPress plugin fails to properly sanitize and escape user-supplied attributes stored in post meta, allowing authenticated contributors and above to inject malicious JavaScript via stored XSS that executes when other users view affected 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
Wp Easy Post TypesWordPress extension
<= 1.4.4CVSS 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 if WP Easy Post Types plugin is installedNavigate to Plugins > Installed Plugins in WordPress admin, or run: wp plugin list --search='wp-easy-post-types'Affected if Plugin named 'WP Easy Post Types' or 'Wp Easy Post Types' appears in the plugin list
-
Verify the installed plugin versionIn WordPress admin, click on the plugin to view details and locate the version number, or inspect the main plugin file header in wp-content/plugins/wp-easy-post-types/Affected if Version displayed is 1.4.4 or lower
-
Confirm the plugin is activeCheck the status column in Plugins > Installed Plugins; the plugin must be activated for the XSS to be exploitableAffected if Plugin shows as 'Active' under the status column
-
Identify post meta fields created by the pluginQuery the wp_postmeta table for meta keys associated with custom post types created by this plugin, or check the plugin settings for custom post type configurationsAffected if Custom post types and their associated meta fields exist in the WordPress database
-
Inspect post meta values for potential XSS payloadsExamine the wp_postmeta table meta_value column for entries containing script tags, event handlers (onclick, onerror, etc.), or javascript: URIs in fields tied to the plugin's post typesAffected if Any meta_value contains unescaped HTML or JavaScript code such as <script>, img onerror=, or similar injection patterns
The environment is affected if WP Easy Post Types version 1.4.4 or lower is installed, active, and contains post meta data with unescaped user-supplied content that could execute malicious JavaScript.
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 · scopedUpgrade to version 1.4.5 or later which includes proper input sanitization and output escaping. If immediate upgrade is not possible, restrict contributor-level access pending the patch.
Latest available version newer than 1.4.4 (check WordPress plugin repository for current version)
- Check the WordPress plugin repository for WP Easy Post Types to identify if a version newer than 1.4.4 is available
- If a newer version exists (such as 1.4.5 or later), update the plugin to the latest available version through WordPress admin dashboard > Plugins > WP Easy Post Types > Update Now
- After updating, verify the fix by confirming the plugin changelog mentions security fixes for XSS vulnerabilities
- Test that authenticated users with contributor-level permissions can no longer inject scripts through post meta fields
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Easy Post Types
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10080 — 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-10080 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