CVE-2024-6568
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 Flamix: Bitrix24 and Contact Form 7 integrations plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 3.1.0. This is due the plugin utilizing mobiledetect without preventing direct access to the files. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website.
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 Flamix WordPress plugin includes the mobilledetect library without proper access controls, allowing unauthenticated attackers to directly access these files and disclose the full server path. This is a classic Full Path Disclosure vulnerability where the third-party library is exposed to direct HTTP requests.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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.
-
Identify Flamix plugin installationEnumerate installed WordPress plugins via the plugins admin interface, wp-cli 'wp plugin list', or by checking the /wp-content/plugins/ directory for folders containing 'flamix' in the nameAffected if The Flamix plugin is installed and active on the WordPress site
-
Locate mobiledetect library filesSearch the Flamix plugin directory for a 'mobiledetect' subdirectory or files named 'Mobile_Detect.php', 'mobiledetect.php', or similar; typical paths include /wp-content/plugins/flamix/mobiledetect/ or nested paths within the plugin structureAffected if The mobilledetect library files exist within the Flamix plugin directory
-
Test direct HTTP access to mobiledetect endpointsSend HTTP GET requests to potential mobiledetect file URLs such as /wp-content/plugins/flamix/mobiledetect/Mobile_Detect.php, /wp-content/plugins/flamix/libs/mobiledetect/mobiledetect.php, or similar URL patterns and examine the response for path disclosure or file contentAffected if Direct HTTP requests to mobiledetect files return successful responses containing PHP code, error messages, or server path information
If the Flamix plugin is present and its mobilledetect library files are directly accessible via HTTP requests, exposing server paths or file contents, the environment is vulnerable to CVE-2024-6568
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 dataAdd .htaccess rules to prevent direct access to the mobiledetect files/directory, or update to a patched version if available. Alternatively, ensure mobiledetect is only loaded through proper PHP includes rather than direct HTTP access.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6568 — 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-6568 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