dbcve.org
Material Design Icons For Page BuildersWordPress extension · Material Design Icons For Page Builders Project

CVE-2023-24382

HIGH · 8.8 CVSS v3.1 Published 2023-02-14
Fix available
A fix is available. Upgrade to 1.4.3 or later.
See remediation →
95/100
Remediation priority · Urgent
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 Photon WP Material Design Icons for Page Builders plugin <= 1.4.2 versions.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Photon WP Material Design Icons for Page Builders plugin affecting versions 1.4.2 and below. The vulnerability allows attackers to induce authenticated users to perform unwanted actions by tricking them into submitting malicious requests, potentially leading to unauthorized configuration changes or data manipulation within the plugin.

MitigationUpdate to a patched version of the plugin if available, or implement anti-CSRF tokens (nonces) on all state-changing operations including form submissions and AJAX requests, and configure SameSite attributes on session cookies.

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
Material Design Icons For Page BuildersWordPress extension
Affected:< 1.4.3

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 installation and version
    Access the WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'Material Design Icons For Page Builders' (or 'Photon WP Material Design Icons for Page Builders'), and note the installed version number.
    Affected if The installed version is 1.4.2 or below.
  2. Confirm plugin is active
    In the WordPress Plugins list, verify that the plugin status shows as 'Active' rather than 'Inactive' or 'Must-Use'.
    Affected if The plugin is active and running version 1.4.2 or below.
  3. Identify state-changing plugin features
    Access the plugin settings page (usually under Settings or the plugin's dedicated menu item in the WordPress admin) and identify any forms, AJAX endpoints, or configuration options that modify plugin data or WordPress settings.
    Affected if The plugin has forms or AJAX actions that perform configuration changes or data manipulation without requiring confirmation.
  4. Inspect for anti-CSRF token presence
    View the page source of the plugin settings page (or any page containing plugin forms), and search for 'wp_nonce', 'nonce', '_wpnonce', or 'token' in the HTML forms and AJAX requests. Also check if the plugin admin pages include WordPress nonces using functions like wp_nonce_field() or wp_nonce_url().
    Affected if Forms and AJAX requests lack nonce tokens or the tokens are missing from critical state-changing operations.
  5. Check session cookie configuration
    Inspect HTTP response headers from the WordPress admin pages using browser developer tools (Network tab) or a command-line tool like curl -I, looking for Set-Cookie headers to verify if SameSite attributes are configured on session cookies.
    Affected if Session cookies lack SameSite attribute or have it set to 'Lax' without additional CSRF protections.

You are affected if the Material Design Icons For Page Builders plugin is active and running version 1.4.2 or below, and the plugin's state-changing operations lack anti-CSRF nonce protections.

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.4.3 or later
Fixed in 1.4.3
Interim mitigation

Update to a patched version of the plugin if available, or implement anti-CSRF tokens (nonces) on all state-changing operations including form submissions and AJAX requests, and configure SameSite attributes on session cookies.

Recommended fix High confidence

Material Design Icons For Page Builders version 1.4.3

  1. Backup your WordPress site database and files before making any changes
  2. Log in to WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Find 'Material Design Icons For Page Builders' (or 'Photon WP Material Design Icons')
  5. Click 'Update now' if an update is available, or manually update to version 1.4.3
  6. Verify the plugin is running version 1.4.3 or later after updating
  7. Test that the plugin functionality works correctly after the update

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

Fix this in Material Design Icons For Page Builders 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-2023-24382 — 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-2023-24382 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