dbcve.org
Endless Posts NavigationWordPress extension · Androidbubbles

CVE-2024-49629

MEDIUM · 6.1 CVSS v3.1 Published 2024-10-20
Fix available
A fix is available. Upgrade to 2.2.8 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in Fahad Mahmood Endless Posts Navigation endless-posts-navigation allows Stored XSS.This issue affects Endless Posts Navigation: from n/a through <= 2.2.7.

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 confidence

CSRF vulnerability in the Endless Posts Navigation WordPress plugin allows attackers to trick authenticated administrators into performing unintended actions that result in Stored XSS. The plugin fails to properly validate anti-CSRF tokens (nonces) on form submissions, enabling malicious script injection.

MitigationImplement WordPress nonces on all admin-facing forms and AJAX actions, and apply proper output escaping/sanitization on stored data display to prevent XSS.

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
Endless Posts NavigationWordPress extension
Affected:< 2.2.8

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Confirm plugin is installed
    Navigate to WordPress admin dashboard > Plugins and verify 'Endless Posts Navigation' by Androidbubbles is listed as an active or installed plugin
    Affected if The plugin appears in the installed plugins list
  2. Identify installed version
    In Plugins list, locate the version number displayed beneath the 'Endless Posts Navigation' plugin name, or check the plugin's main PHP file header for 'Version:' tag
    Affected if Version number is less than 2.2.8 (e.g., 2.2.7, 2.2.6, etc.)
  3. Inspect admin form nonce implementation
    Access the plugin source code (wp-content/plugins/endless-posts-navigation) and examine admin-facing PHP files for form submissions. Search for 'wp_nonce_field' or 'wp_nonce' calls on forms that handle plugin settings or post navigation options
    Affected if Forms that process admin actions lack nonce validation or use an incorrect/removed nonce check
  4. Verify stored data output escaping
    Examine PHP files that display saved plugin options or post navigation content. Look for functions like echo, print, or output statements that render stored values without esc_html(), esc_attr(), or similar sanitization functions
    Affected if Stored data is output without proper escaping, allowing injected scripts to execute in admin or frontend views

If the Endless Posts Navigation plugin is installed at a version below 2.2.8 and admin forms lack proper nonce validation, the environment is vulnerable to CVE-2024-49629

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.2.8 or later
Fixed in 2.2.8
Interim mitigation

Implement WordPress nonces on all admin-facing forms and AJAX actions, and apply proper output escaping/sanitization on stored data display to prevent XSS.

Recommended fix High confidence

2.2.8

  1. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  2. Find 'Endless Posts Navigation' in the plugin list
  3. Click 'Update now' if an update is available, or manually update to version 2.2.8
  4. Verify the update completed successfully

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Endless Posts Navigation Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-49629 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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