Dean Logan Wp People PluginPlugin / extension · WordPress
CVE-2008-0845
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 · uneditedSQL injection vulnerability in wp-people-popup.php in Dean Logan WP-People plugin 1.6.1 for WordPress allows remote attackers to execute arbitrary SQL commands via the person parameter.
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 confidenceSQL injection vulnerability in the wp-people-popup.php file of the WP-People plugin versions 1.6.1 and earlier for WordPress. The 'person' parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL commands.
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
Dean Logan Wp People PluginPlugin / extension
= 1.6.1CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 WP-People plugin is installedCheck for the wp-people plugin directory at /wp-content/plugins/wp-people/ or look for the plugin in WordPress admin under PluginsAffected if The plugin directory or plugin entry exists in the WordPress installation
-
Identify installed plugin versionCheck the main plugin file (wp-people.php or similar) for the version comment/header, or look at the plugin metadata in WordPress admin Plugins pageAffected if The version is 1.6.1 or any version earlier than 1.6.1
-
Confirm vulnerable file existsVerify wp-people-popup.php exists in the plugin directory at /wp-content/plugins/wp-people/wp-people-popup.phpAffected if The file wp-people-popup.php is present in the plugin directory
-
Check if plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and verify the WP-People plugin status, or query the wp_options table for active_pluginsAffected if The WP-People plugin is activated on the WordPress site
-
Verify endpoint is accessibleAttempt to access the vulnerable URL pattern: /wp-content/plugins/wp-people/wp-people-popup.php?person=test or check server access logs for requests to this fileAffected if The wp-people-popup.php file is accessible via web requests
The environment is affected if the WP-People plugin versions 1.6.1 or earlier is installed, activated, and the wp-people-popup.php file is accessible on the server.
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 the WP-People plugin, or disable and remove the plugin if no patch is available. Until patched, consider restricting access to the affected endpoint via web server configuration.
Fix this in Dean Logan Wp People Plugin
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-0845 — 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-2008-0845 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