Phpinfo WpWordPress extension · Exeebit
CVE-2024-35776
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 · uneditedExposure of Sensitive Information to an Unauthorized Actor vulnerability in Exeebit phpinfo() WP.This issue affects phpinfo() WP: from n/a through 5.0.
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 Exeebit phpinfo() WP plugin (versions through 5.0) exposes the PHP phpinfo() function to unauthenticated users, revealing sensitive system configuration details including PHP version, loaded extensions, server paths, environment variables, and potentially credentials or paths that could aid further attacks.
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
Phpinfo WpWordPress extension
<= 5.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Confirm Exeebit Phpinfo Wp plugin is installedAccess your WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Exeebit Phpinfo Wp' in the plugin list. Alternatively, check the wp-content/plugins directory for a folder named 'exebit-phpinfo-wp' or similar.Affected if The plugin appears in the installed plugins list
-
Identify the installed plugin versionIn the WordPress admin under Plugins > Installed Plugins, click on the plugin details for Exeebit Phpinfo Wp and note the version number displayed.Affected if The version is 5.0 or lower (versions through 5.0 are affected)
-
Test unauthenticated access to phpinfo() outputUsing a web browser or curl, attempt to access the plugin's phpinfo() page directly without logging in. Common URL patterns include /wp-content/plugins/exebit-phpinfo-wp/phpinfo.php or /?page=exebit-phpinfo-wp. Try accessing any endpoint that displays PHP configuration information.Affected if The phpinfo() page loads and displays PHP version, extensions, server paths, or environment variables without requiring authentication
-
Inspect plugin files for phpinfo() exposureUsing file access or FTP, examine the main plugin file in wp-content/plugins/exebit-phpinfo-wp/ for calls to phpinfo(). Look for direct phpinfo() function calls that execute without capability checks or authentication requirements.Affected if The plugin contains an unprotected phpinfo() call accessible to any visitor
You are affected if the Exeebit Phpinfo Wp plugin (version 5.0 or lower) is installed and its phpinfo() output is accessible to unauthenticated users, revealing system configuration details.
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 dataRemove or disable the phpinfo() function call from the plugin, or restrict access to require authentication. If phpinfo() functionality is not essential, remove the plugin entirely.
Fix this in Phpinfo Wp
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35776 — 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-35776 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