dbcve.org
Ajax Load MoreWordPress extension · Connekthq

CVE-2025-47630

MEDIUM · 5.4 CVSS v3.1 Published 2025-05-07
Fix available
A fix is available. Upgrade to after 7.3.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Darren Cooney Ajax Load More ajax-load-more allows Stored XSS.This issue affects Ajax Load More: from n/a through <= 7.3.1.2.

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 confidence

Stored XSS vulnerability in the Ajax Load More WordPress plugin (versions <= 7.3.1.2) allows attackers to inject malicious JavaScript through plugin input parameters that are not properly sanitized before being stored and rendered in web pages.

MitigationImplement proper input validation and output encoding using WordPress sanitization functions (sanitize_text_field, esc_html, esc_attr) on all user-supplied data before storage and display; update to patched version if available.

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
Ajax Load MoreWordPress extension
Affected:<= 7.3.1

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
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 checks

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

  1. Verify plugin version
    Navigate to Plugins > Installed Plugins in WordPress admin, locate 'Ajax Load More by Connekthq', and check the version number displayed. Alternatively, check the plugin's main PHP file (typically ajax-load-more.php) for the 'Version' header in the plugin comment block.
    Affected if The installed version is 7.3.1 or lower.
  2. Identify plugin shortcodes in use
    Search your posts, pages, and widgets for the [ajax_load_more] shortcode. Also check if the plugin's custom post type 'alm' is being used by viewing any entries under 'Ajax Load More' in the admin menu.
    Affected if The shortcode or custom post type is actively used on the site, as this provides the rendering context for stored XSS.
  3. Review plugin settings for custom inputs
    Go to Ajax Load More > Settings in the WordPress admin panel. Check all tabs (General, Repeater Templates, Shortcode Builder) for any fields that accept custom labels, class names, or custom parameters that could store user-supplied data.
    Affected if Custom parameters or labels are configured and saved through the plugin settings.
  4. Inspect database for stored content
    Access the WordPress database (via phpMyAdmin or CLI) and examine the wp_postmeta table for entries with meta_key containing 'ajax_load_more' or 'alm'. Also check the alm_posts table if it exists. Look for any HTML or script tags in the meta_value fields.
    Affected if Stored meta values contain unescaped HTML or JavaScript characters like <script>, javascript:, or event handlers like onerror/onclick.
  5. Check front-end rendering of plugin elements
    View the source code of a page containing the Ajax Load More shortcode. Search for the rendered output and verify if the shortcode attributes (container_type, button_label, etc.) are properly escaped using esc_attr() or similar functions.
    Affected if The rendered HTML shows raw attribute values without proper HTML encoding (e.g., quotes are not escaped as &quot;).

If the plugin version is 7.3.1 or lower AND the plugin is actively displaying content through shortcodes or custom post types, the environment is likely affected by this stored XSS vulnerability.

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.

From vendor data
Upgrade available Upgrade to a release after 7.3.1
Interim mitigation

Implement proper input validation and output encoding using WordPress sanitization functions (sanitize_text_field, esc_html, esc_attr) on all user-supplied data before storage and display; update to patched version if available.

Fix this in Ajax Load More Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47630 — 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-2025-47630 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