Wp Easy Post TypesWordPress extension · Newsignature

CVE-2024-10078

MEDIUM · 6.3 CVSS v3.1 Published 2024-10-18

Fix available

A fix is available. Upgrade to after 1.4.4 or later.

See remediation →

69/100

Remediation priority · Elevated

Remotely reachable Zero-click

Official description

NVD · unedited

The WP Easy Post Types plugin for WordPress is vulnerable to unauthorized access, modification, and loss of data due to a missing capability check on multiple functions in all versions up to, and including, 1.4.4. This makes it possible for authenticated attackers, with subscriber-level access and above, to add, modify, or delete plugin options and posts.

Technical summary

dbcve analysis · high confidence

The WP Easy Post Types WordPress plugin lacks proper capability checks on multiple functions, allowing authenticated users with subscriber-level access to add, modify, or delete plugin options and posts. This is an Insecure Direct Object Reference (IDOR) / broken access control vulnerability in versions up to 1.4.4.

MitigationUpdate to a patched version of the plugin once released, or audit and add proper WordPress capability checks (e.g., current_user_can()) to all sensitive functions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Wp Easy Post TypesWordPress extension

Affected:<= 1.4.4

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: Low
User interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify plugin version

Locate the WP Easy Post Types plugin in your WordPress installation (typically in wp-content/plugins/) and read the plugin header comment to find the Version field, or use 'wp plugin list' via WP-CLI to list installed plugins with their versions

Affected if The installed version is 1.4.4 or lower
Verify low-privilege user existence

Check your WordPress user roles by reviewing the Users panel in wp-admin or querying the wp_users and wp_usermeta tables. Look for users assigned the Subscriber role specifically

Affected if There are users with Subscriber-level access or other low-privilege roles active on the site
Test plugin function access with low-privilege account

Log in as a subscriber-level user and attempt to access plugin settings pages or post management features (e.g., /wp-admin/admin.php?page=wp-easy-post-types or similar plugin admin URLs)

Affected if A subscriber-level user can access or modify plugin options, or can create/edit/delete posts through the plugin without receiving an access denied error
Inspect plugin code for capability checks

Examine the main plugin PHP file for presence of WordPress capability checks like 'current_user_can()' before sensitive operations (add, modify, delete options or posts)

Affected if The plugin code lacks capability checks before sensitive functions, allowing subscriber-level users to perform admin-level actions

You are affected if the WP Easy Post Types plugin version is 1.4.4 or lower AND low-privilege users (especially subscribers) can access plugin settings or post management features without proper authorization.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Upgrade available Upgrade to a release after 1.4.4

Interim mitigation

Update to a patched version of the plugin once released, or audit and add proper WordPress capability checks (e.g., current_user_can()) to all sensitive functions.

Fix this in Wp Easy Post Types Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing3.0 h
Review / QA2.0 h

14.0 hours of engineering $2,490

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2024-10078 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-10078 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-10078?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsUpgrade to after 1.4.4 or later

Severity 6.3 Medium

Exploit likelihood EPSS, next 30 days 0.4%

Affects: Wp Easy Post Types

Remediation

Need this fixed?

Fix this in Wp Easy Post Types 14 hrs · Moderate

Typical engagement from $2,490

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2024-10078 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

CVSS 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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References