CVE-2025-58024
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 Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in UnboundStudio Accordion FAQ allows PHP Local File Inclusion. This issue affects Accordion FAQ: from n/a through 2.2.1.
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 · moderate confidenceThis is a PHP Local File Inclusion (LFI) vulnerability in the UnboundStudio Accordion FAQ plugin (versions up to 2.2.1). The plugin fails to properly validate or sanitize input used in include/require statements, allowing attackers to manipulate file path parameters and include arbitrary PHP files from the server filesystem, potentially leading to remote code execution.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Accordion FAQ plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Accordion FAQ' by UnboundStudio. Note its active/inactive status.Affected if The plugin is installed and active
-
Check installed plugin versionClick 'View Details' on the Accordion FAQ plugin in the WordPress plugins page to display the version number, or check the plugin's main PHP file header for 'Version:' comment.Affected if Version is 2.2.1 or lower (any version up to and including 2.2.1 is affected)
-
Identify exposed include/require parametersReview plugin source code in wp-content/plugins/accordion-faq/ directory. Search for PHP 'include', 'require', 'include_once', or 'require_once' statements that use variables (e.g., include($var); or require $_GET['param'];). These indicate potential LFI vectors.Affected if Plugin code contains include/require statements using unsanitized user input from request parameters (GET, POST, or COOKIE)
-
Check PHP configuration for allow_url_includeCreate a PHP info page (<?php phpinfo(); ?>) or check php.ini for the 'allow_url_include' directive setting.Affected if allow_url_include is enabled (On), which would allow inclusion of remote URLs in addition to local files, increasing exploit severity
User is affected if Accordion FAQ plugin versions 2.2.1 or lower are installed and active, with vulnerable include/require code paths present in the plugin.
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 to a patched version of Accordion FAQ when available. Until then, implement strict input validation on all file inclusion parameters and restrict file access permissions to prevent inclusion of sensitive system files.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58024 — 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-2025-58024 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