Wp Easy Post TypesWordPress extension · Newsignature
CVE-2024-10079
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 PHP Object Injection in versions up to, and including, 1.4.4 via deserialization of untrusted input from the 'text' parameter in the 'ajax_import_content' function. This allows authenticated attackers, with subscriber-level permissions and above, to inject a PHP Object. No POP chain is present in the vulnerable plugin. 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 WP Easy Post Types WordPress plugin is vulnerable to PHP Object Injection via unsafe deserialization of the 'text' parameter in the ajax_import_content function. Authenticated attackers with subscriber-level permissions can inject arbitrary PHP objects. While the plugin itself lacks a POP chain, additional plugins or themes on the target WordPress installation could provide one, enabling arbitrary file deletion, data exfiltration, or code execution.
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
- 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 WP Easy Post Types plugin is installedCheck the WordPress plugins directory for the 'wp-easy-post-types' folder, or run 'wp plugin list' via WP-CLI, or inspect /wp-content/plugins/ directory for the plugin files.Affected if The plugin folder exists in the WordPress plugins directory.
-
Determine installed plugin versionOpen the main plugin file (usually wp-easy-post-types/wp-easy-post-types.php) and locate the 'Version' header in the plugin comment block, or use 'wp plugin get wp-easy-post-types' via WP-CLI.Affected if The version listed is 1.4.4 or lower.
-
Confirm the ajax_import_content function is accessibleInspect the plugin PHP files for the ajax_import_content function and its associated wp_ajax or wp_ajax_nopriv hooks. Check if the function is registered with an action that does not require elevated privileges (such as wp_ajax_nopriv or a capability check below 'edit_posts').Affected if The ajax_import_content function is hooked to an action accessible to subscriber-level users without proper capability checks.
-
Identify subscriber-level user accountsIn WordPress admin, go to Users > All Users and review the role column, or query the wp_users and wp_usermeta tables to list users with the 'subscriber' role.Affected if Any user accounts exist with the subscriber role.
-
Audit for potential POP chain sourcesReview all installed plugins and themes for known PHP Object Injection POP chains. Check plugin versions against known vulnerabilities, or use security scanning tools that detect unsafe deserialization patterns in other active plugins.Affected if Additional plugins or themes with exploitable unserialize() calls and available POP chains are installed alongside the vulnerable plugin.
A user is affected if the WP Easy Post Types plugin version is 1.4.4 or lower AND the ajax_import_content function is exposed to subscriber-level users, creating a PHP Object Injection vector that could be escalated via POP chains in other plugins.
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.
From vendor dataUpdate the WP Easy Post Types plugin to a version beyond 1.4.4 when available. Until then, restrict or disable subscriber-level access to the affected ajax_import_content functionality and review installed plugins/themes for potential POP chains.
Fix this in Wp Easy Post Types
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10079 — 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-10079 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