dbcve.org
Fg DrupalWordPress extension · Fredericgilles

CVE-2024-31247

HIGH · 7.5 CVSS v3.1 Published 2024-04-10
Fix available
A fix is available. Upgrade to 3.71.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Insertion of Sensitive Information into Log File vulnerability in Frédéric GILLES FG Drupal to WordPress.This issue affects FG Drupal to WordPress: from n/a through 3.70.3.

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

The FG Drupal to WordPress plugin (versions up to 3.70.3) has a vulnerability where sensitive information is being written to log files. This allows unauthorized actors who can access log files to potentially obtain credentials, session tokens, or other sensitive data that may have been logged during the migration process.

MitigationReview and sanitize all logging statements in the plugin to ensure no sensitive data (credentials, tokens, PII) is written to log files. Implement proper log sanitization or disable verbose logging in production environments.

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
Fg DrupalWordPress extension
Affected:< 3.71.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Check if FG Drupal to WordPress plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'FG Drupal to WordPress' or 'Fredericgilles Fg Drupal'. Alternatively, check the plugin directory wp-content/plugins/ for a folder starting with 'fg-drupal'.
    Affected if The plugin is installed and its version is below 3.71.0
  2. Determine installed plugin version
    In the WordPress plugin list, click on the plugin to view details and read the version number from the plugin header. Compare this version against the affected range (versions < 3.71.0).
    Affected if Installed version is 3.70.3 or lower
  3. Locate plugin-generated log files
    Check common WordPress log locations: wp-content/debug.log, wp-content/plugins/fg-drupal-to-wordpress/logs/, and the WordPress uploads directory. Also check any custom log paths configured in the plugin settings.
    Affected if Log files exist and were created during or after a migration run
  4. Search log files for sensitive information
    Open the log files using a text editor or grep command and search for patterns indicating sensitive data: keywords like 'password', 'passwd', 'token', 'session', 'credential', 'secret', 'key', 'api', or connection strings that may contain authentication details.
    Affected if Log files contain strings matching patterns for credentials, tokens, passwords, or other sensitive data

You are affected if the FG Drupal to WordPress plugin is installed at version below 3.71.0 and log files exist that contain sensitive data such as credentials, tokens, or authentication information.

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

Review and sanitize all logging statements in the plugin to ensure no sensitive data (credentials, tokens, PII) is written to log files. Implement proper log sanitization or disable verbose logging in production environments.

Recommended fix Moderate confidence

3.71.0 or later

  1. 1. Back up your WordPress site and database before performing any updates.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Find 'FG Drupal to WordPress' in the list.
  5. 5. If an update is available, click 'Update Now' to upgrade to version 3.71.0 or later.
  6. 6. After updating, verify the plugin is functioning correctly by running a test migration.

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

Fix this in Fg Drupal 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-31247 — 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-31247 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