CVE-2024-3810
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 · uneditedThe Salient Shortcodes plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.5.3 via the 'icon' shortcode 'image' 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 confidenceThe Salient Shortcodes WordPress plugin contains a Local File Inclusion (LFI) vulnerability in the 'icon' shortcode's 'image' attribute, affecting all versions up to 1.5.3. Authenticated attackers with contributor-level or higher permissions can include and execute arbitrary files on the server, leading to potential code execution, data exfiltration, and access control bypass.
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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Salient Shortcodes plugin is installedNavigate to WordPress admin Dashboard > Plugins > Installed Plugins and look for 'Salient Shortcodes' in the list. Alternatively, check the /wp-content/plugins/ directory for a salient-shortcodes folder.Affected if The Salient Shortcodes plugin is present in the WordPress installation
-
Identify installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins. Find Salient Shortcodes and view the version number displayed beneath the plugin name. Or check the main plugin file header in /wp-content/plugins/salient-shortcodes/salient-shortcodes.php for the Version: field.Affected if The version number is 1.5.3 or lower (any version up to and including 1.5.3)
-
Confirm shortcode functionality is activeCheck if the plugin is activated in Plugins > Installed Plugins - the plugin must show as 'Active' beneath its name. Also verify that the theme or other plugins are not explicitly disabling shortcodes that might call this plugin.Affected if The plugin is activated and the icon shortcode functionality is available for use
-
Audit user permissions for contributor-level accessReview WordPress user roles at Users > All Users. Check if any users have the 'Contributor' role or higher (Author, Editor, Administrator). These roles can access the vulnerable shortcode.Affected if There exist user accounts with Contributor, Author, Editor, or Administrator roles who can access the WordPress admin or use the shortcode via front-end submission
A user is affected if the Salient Shortcodes plugin is installed, activated, running version 1.5.3 or lower, and any contributor-level or higher user account exists on the site.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Salient Shortcodes to version 1.5.4 or later immediately. If the plugin is abandoned or no patch is available, remove it entirely and seek alternative solutions.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-3810 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-3810 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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