CVE-2025-52806
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 eyecix JobSearch wp-jobsearch allows PHP Local File Inclusion.This issue affects JobSearch: from n/a through < 3.0.8.
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 confidenceLocal File Inclusion vulnerability in the eyecix JobSearch WordPress plugin allows attackers to include arbitrary PHP files from the server file system via improper control of filename parameters in include/require statements, 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.
-
Locate the JobSearch plugin installationCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'jobsearch' or similar naming convention for the eyecix JobSearch pluginAffected if The plugin folder exists on the server
-
Determine the installed plugin versionOpen the main plugin file (typically jobsearch.php or index.php inside the plugin folder) and look for the 'Version' header in the plugin comments, or check readme.txt for the version numberAffected if The version number returned is lower than 3.0.8
-
Verify the plugin is activeIn the WordPress admin dashboard, go to Plugins > Installed Plugins and confirm whether the JobSearch plugin is activatedAffected if The plugin is currently active and the version is below 3.0.8
-
Identify if the vulnerable parameter is accessibleReview web server logs or access logs for requests to the plugin's PHP files that include the 'filename' or similar parameter used in include/require statements. Check if any custom endpoints or AJAX handlers are exposed.Affected if The vulnerable endpoint is accessible (no access restrictions on the affected PHP files) and the plugin version is below 3.0.8
A user is affected if the JobSearch plugin is installed, active, and the version is below 3.0.8, with the vulnerable file inclusion parameter exposed.
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 · scopedUpdate the JobSearch plugin to version 3.0.8 or later to patch the file inclusion vulnerability. If immediate update is not possible, restrict access to the affected endpoint via web server configuration.
JobSearch version 3.0.8
- 1. Backup your WordPress database and files before proceeding
- 2. Navigate to the WordPress admin dashboard
- 3. Go to Plugins > Installed Plugins
- 4. Find the JobSearch plugin (wp-jobsearch)
- 5. If an update to version 3.0.8 or later is available, click 'Update Now'
- 6. Alternatively, download version 3.0.8 from a trusted source and upload it via Plugins > Add New > Upload Plugin
- 7. After upgrading, verify the plugin is functioning correctly and test that the file inclusion vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52806 — 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-52806 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