CVE-2024-31300
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in appscreo Easy Social Share Buttons allows PHP Local File Inclusion.This issue affects Easy Social Share Buttons: from n/a through 9.4.
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 confidenceA Path Traversal vulnerability in Easy Social Share Buttons plugin for WordPress allows remote attackers to perform Local File Inclusion (LFI) by manipulating path parameters to access restricted directories and include arbitrary PHP files. The lack of proper input sanitization on file path parameters enables attackers to traverse the filesystem using '..' sequences and include local PHP files.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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 Easy Social Share Buttons plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Easy Social Share Buttons' in the list. Alternatively, check the wp-content/plugins/ directory for the easy-social-share-buttons folder.Affected if The plugin is present in the WordPress installation
-
Identify the installed plugin versionIn WordPress admin, click on the plugin from the Installed Plugins list to view details, or open the main plugin PHP file (e.g., easy-social-share-buttons.php) and look for the 'Version' header in the plugin comments.Affected if The installed version matches or falls within an affected version range (compare your version to the patched version once known)
-
Inspect HTTP traffic for path parameter manipulationMonitor HTTP requests to the site for parameters that accept file paths, looking for patterns like '..' sequences (e.g., ../../wp-config.php) in query strings or POST data.Affected if Requests contain directory traversal patterns directed at the plugin's endpoints
-
Review access logs for LFI attemptsExamine web server access logs (Apache error.log, Nginx access.log, or WordPress debug.log) for entries containing '..' or '../' patterns targeting plugin-related URLs.Affected if Log entries show traversal attempts to plugin paths or includes
The environment is affected if the Easy Social Share Buttons plugin is installed and the installed version is lower than the patched version, or if suspicious path traversal patterns are observed in HTTP requests or logs.
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 dataUpdate Easy Social Share Buttons to the latest patched version. Until then, disable the plugin or implement WAF rules to block directory traversal patterns in HTTP requests.
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31300 — 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-31300 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