EnfoldWordPress extension · Kriesi
CVE-2024-13695
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 Enfold theme for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 6.0.9 via the 'attachment_id' parameter. This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.
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 Enfold WordPress theme contains a Server-Side Request Forgery (SSRF) vulnerability in all versions up to 6.0.9. The flaw allows authenticated users with Subscriber-level access or higher to manipulate the 'attachment_id' parameter to cause the server to make arbitrary web requests to internal or external locations, potentially exposing internal services and data.
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
EnfoldWordPress extension
< 7.0.0CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check Enfold theme versionLocate the Enfold theme in wp-content/themes/enfold/ and read the version from style.css header or theme.jsonAffected if The installed version is below 7.0.0 (specifically 6.0.9 or earlier)
A user is affected if the Enfold theme version is below 7.0.0 AND the WordPress site allows user registration with Subscriber-level or higher access, enabling authenticated attackers to exploit the attachment_id parameter for SSRF.
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.
dbcve · scoped7.0.0
Update the Enfold theme to version 6.1 or later to remediate this SSRF vulnerability. As a secondary measure, restrict user registration to trusted roles and consider implementing network-level controls to prevent the web server from connecting to internal services.
Enfold theme version 7.0.0 or later
- Backup the entire WordPress site (database and files) before proceeding with any updates
- Obtain the Enfold theme version 7.0.0 or later from the official source (ThemeForest or the vendor's website)
- Navigate to WordPress Dashboard > Appearance > Themes
- Deactivate the current Enfold theme or replace it with the updated version
- Install and activate the new Enfold 7.0.0+ theme version
- Verify that the site loads correctly and all critical functionality works as expected
- Confirm that the 'attachment_id' parameter is no longer vulnerable to SSRF attacks
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Enfold
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13695 — 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-13695 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