dbcve.org
PeepsoWordPress extension

CVE-2024-7426

MEDIUM · 5.3 CVSS v3.1 Published 2024-09-25
Fix available
A fix is available. Upgrade to 6.4.6.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The Community by PeepSo – Social Network, Membership, Registration, User Profiles plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 6.4.6.0. This is due to the plugin displaying errors and allowing direct access to the sse.php file. 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 confidence

The PeepSo WordPress plugin (versions up to 6.4.6.0) contains a file called sse.php that can be accessed directly without proper initialization, causing PHP error messages to be displayed which reveal the full server filesystem path of the web application.

MitigationUpdate the PeepSo plugin to version 6.4.6.1 or later. Alternatively, restrict direct access to the sse.php file via .htaccess rules or web server configuration to prevent unauthenticated access.

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
PeepsoWordPress extension
Affected:< 6.4.6.0

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if PeepSo plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'PeepSo' in the list of installed plugins.
    Affected if PeepSo is not found in the WordPress plugins list, then this CVE does not apply.
  2. Determine the installed PeepSo version
    In the WordPress admin, go to Plugins > Installed Plugins. Find PeepSo and view the version number displayed below the plugin name. Alternatively, check the file /wp-content/plugins/peepso-core/readme.txt for the 'Stable tag' entry.
    Affected if The installed version is less than 6.4.6.0, meaning the version falls within the affected range.
  3. Verify sse.php file exists
    Check for the presence of the file at /wp-content/plugins/peepso-core/lib/sse.php or similar path within the WordPress plugins directory. Use file manager or an FTP client to locate it.
    Affected if The sse.php file does not exist, then the vulnerability cannot be triggered.
  4. Test direct access to sse.php for path disclosure
    Using a web browser or curl, make a direct HTTP request to the sse.php file (for example: https://yourwebsite.com/wp-content/plugins/peepso-core/lib/sse.php). Observe if PHP error messages or path information is displayed in the response.
    Affected if The response contains PHP error messages, warnings, or reveals the absolute server filesystem path (such as /var/www/html/...), then the vulnerability is present.

A user is affected if PeepSo version is below 6.4.6.0 AND the sse.php file is directly accessible, causing path disclosure in error messages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.4.6.0 or later
Fixed in 6.4.6.0
Interim mitigation

Update the PeepSo plugin to version 6.4.6.1 or later. Alternatively, restrict direct access to the sse.php file via .htaccess rules or web server configuration to prevent unauthenticated access.

Recommended fix High confidence

PeepSo plugin version 6.4.6.0 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Community by PeepSo' plugin
  4. Click 'Update Now' if an update is available, or manually upload version 6.4.6.0 or later from wordpress.org/plugins/peepso
  5. Verify the plugin updated successfully to version 6.4.6.0 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Peepso Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7426 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-7426 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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