CVE-2024-54311
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 · uneditedMissing Authorization vulnerability in i.lychkov Mark New Posts mark-new-posts allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Mark New Posts: from n/a through <= 7.5.1.
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 confidenceMissing Authorization vulnerability in the Mark New Posts WordPress plugin (versions <= 7.5.1) allows unauthorized users to exploit incorrectly configured access control security levels. This likely means certain administrative functions or post-marking actions lack proper capability checks or nonce validation, permitting lower-privileged users to perform actions reserved for administrators.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
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 Mark New Posts plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Mark New Posts' in the list. Alternatively, check the /wp-content/plugins/mark-new-posts/ directory exists.Affected if The plugin is not installed or has been removed entirely (not affected)
-
Check installed plugin versionIn WordPress adminPlugins list, find 'Mark New Posts' and note the version number displayed below the plugin name. Compare against 7.5.1.Affected if Version is 7.5.1 or lower (vulnerable range)
-
Identify accessible admin endpointsReview the plugin directory for PHP files containing AJAX handlers or admin_init hooks. Look for functions that process user requests without calling current_user_can() or wp_verify_nonce() before performing administrative actions.Affected if Plugin code contains admin action handlers lacking capability checks or nonce validation
-
Test lower-privileged user accessCreate or use a WordPress user account with subscriber-level role (not administrator). Attempt to access plugin features meant for admins, such as marking posts as read or modifying global notification settings, via direct URL or AJAX calls.Affected if A lower-privileged user (e.g., subscriber) can successfully trigger admin-only functions
The environment is affected if the Mark New Posts plugin is installed with version 7.5.1 or lower, and administrative functions lack proper capability checks or nonce validation, allowing privilege escalation.
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 to the latest version of Mark New Posts if a patch is available; otherwise, audit the plugin code for all hooks and functions missing capability checks (e.g., current_user_can()) or nonce validation, and add proper authorization controls.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54311 — 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-54311 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