dbcve.org
Json Content ImporterWordPress extension

CVE-2024-38723

MEDIUM · 6.4 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to 1.6.0 or later.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Server-Side Request Forgery (SSRF) vulnerability in Bernhard Kux JSON Content Importer.This issue affects JSON Content Importer: from n/a through 1.5.6.

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

Server-Side Request Forgery (SSRF) vulnerability in the JSON Content Importer WordPress plugin allows attackers to make the server perform requests to arbitrary URLs, potentially accessing internal infrastructure, cloud metadata endpoints, or sensitive internal services.

MitigationUpdate to the latest patched version of JSON Content Importer (1.5.7+) and implement strict URL allowlist validation to restrict requests to trusted, externally-accessible domains only.

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
Json Content ImporterWordPress extension
Affected:< 1.6.0

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 JSON Content Importer plugin is installed
    Check the WordPress plugins directory (wp-content/plugins) or view installed plugins in WordPress admin under Plugins > Installed Plugins for 'Json Content Importer' or 'json-content-importer'
    Affected if Plugin is present in the installation
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and look at the version number listed for JSON Content Importer, or inspect the plugin's main PHP file for the 'Version' header in the plugin comment block
    Affected if Version is less than 1.6.0 (vulnerable versions: 1.5.7 and below)
  3. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that JSON Content Importer shows as 'Active'
    Affected if Plugin is actively installed and enabled
  4. Identify shortcode usage accepting external URLs
    Search WordPress posts, pages, and widgets for the '[jsoncontentimporter]' or similar shortcode that accepts a 'url' or 'endpoint' parameter, or check the plugin settings pages for URL input fields
    Affected if Shortcode or settings allow user-controlled URL input that could be exploited for SSRF
  5. Review access to internal infrastructure potential
    Examine any publicly accessible endpoints or API configurations where this plugin could be used to probe internal services, cloud metadata endpoints (e.g., http://169.254.169.254), or internal network resources
    Affected if Plugin can be invoked by unauthenticated or low-privilege users to make arbitrary HTTP requests

If JSON Content Importer plugin version is below 1.6.0, is active, and accepts external URL input through shortcodes or settings, the installation is vulnerable to SSRF attacks.

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 1.6.0 or later
Fixed in 1.6.0
Interim mitigation

Update to the latest patched version of JSON Content Importer (1.5.7+) and implement strict URL allowlist validation to restrict requests to trusted, externally-accessible domains only.

Recommended fix Moderate confidence

1.6.0

  1. Update the JSON Content Importer WordPress plugin to version 1.6.0 or later via the WordPress admin dashboard under Plugins > Updates, or manually download and install version 1.6.0 from the WordPress plugin repository
  2. After upgrading, verify the plugin is functioning correctly by testing any JSON import functionality that was previously used
  3. Ensure the WordPress core and other plugins are also kept up to date

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

Fix this in Json Content Importer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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