dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2024-3812

HIGH · 7.5 CVSS v3.1 Published 2024-05-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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
The Salient Core plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.0.7 via the 'nectar_icon' shortcode 'icon_linea' attribute. This makes it possible for authenticated attackers, with contributor-level and above permissions, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where php file type can be uploaded and included.

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

The Salient Core WordPress plugin is vulnerable to Local File Inclusion (LFI) via the 'nectar_icon' shortcode's 'icon_linea' attribute in versions up to 2.0.7. Authenticated attackers with contributor-level or higher permissions can include arbitrary files from the server, enabling PHP code execution and potential bypass of access controls.

MitigationUpdate Salient Core plugin to version 2.0.8 or later. Until patched, restrict or monitor contributor-level user accounts and consider disabling the nectar_icon shortcode.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/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. Check Salient Core plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Salient Core and read the Version number. Alternatively, check the plugin's main PHP file header or composer.json for the version.
    Affected if Version is 2.0.7 or lower (the plugin is vulnerable up to version 2.0.7)
  2. Verify nectar_icon shortcode is registered
    Search the Salient Core plugin files for 'add_shortcode' calls containing 'nectar_icon'. In WordPress, you can also use a plugin like WP-CLI or a shortcode scanner to list registered shortcodes.
    Affected if The 'nectar_icon' shortcode exists and is loaded (the vulnerability lives in this shortcode)
  3. Identify users with contributor-level or higher permissions
    In WordPress admin, go to Users > All Users and review the Role column. Contributors, Authors, Editors, and Administrators have permissions that can trigger the vulnerable code path.
    Affected if Any user account has Contributor, Author, Editor, or Administrator role (these roles can exploit the flaw)
  4. Check if shortcode is actively used in content
    Search WordPress database (wp_posts table) or use a plugin to search post content for '[nectar_icon' shortcode usage. Also check page builder content areas where shortcodes may be embedded.
    Affected if The nectar_icon shortcode with icon_linea attribute is present in any post, page, or widget content (exploitation requires the shortcode to be processed)

User is affected if Salient Core plugin version is 2.0.7 or lower AND the nectar_icon shortcode is registered and accessible to contributor-level users.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Salient Core plugin to version 2.0.8 or later. Until patched, restrict or monitor contributor-level user accounts and consider disabling the nectar_icon shortcode.

Recommended fix Moderate confidence

Salient Core version 2.0.8 or later

  1. Update the Salient Core WordPress plugin to the latest available version
  2. If automatic updates are not enabled, navigate to Plugins > All Plugins in WordPress admin and update Salient Core manually
  3. After updating, verify the 'nectar_icon' shortcode 'icon_linea' attribute no longer accepts arbitrary file paths
  4. Confirm no unauthorized code execution has occurred by reviewing server files for any suspicious PHP files that may have been uploaded prior to the fix
  5. Consider reviewing user accounts with contributor-level or higher permissions to ensure no compromise

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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