Wp CachecomWordPress extension · Kenthhagstrom
CVE-2023-34177
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Kenth Hagström WP-Cache.Com plugin <= 1.1.1 versions.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the WP-Cache.Com plugin versions 1.1.1 and below allows remote attackers to trick authenticated administrators into performing unintended cache configuration changes or other administrative actions via maliciously crafted requests.
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
Wp CachecomWordPress extension
<= 1.1.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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 WP-Cache.Com plugin is installedCheck your WordPress plugins directory or admin panel for 'Kenthhagstrom Wp Cachecom' or 'WP-Cache.Com' in the list of installed pluginsAffected if The plugin is present in the installation
-
Determine installed plugin versionLocate the plugin header in the main plugin file (typically in wp-content/plugins/wp-cachecom/ or similar path) and read the 'Version:' field, or check via WordPress admin plugins listAffected if Version number is 1.1.1 or lower
-
Confirm plugin is activeAccess WordPress admin dashboard and check if the plugin is activated in the Plugins list, or query the wp_options table for active_pluginsAffected if Plugin is activated and accessible to administrators
-
Inspect admin settings forms for CSRF protectionExamine the plugin PHP source code for all form submissions and state-changing actions; search for wp_nonce_field, wp_verify_nonce, or nonce verification on settings update handlersAffected if No anti-CSRF tokens are found in settings forms or AJAX endpoints
-
Check for Origin/Referer header validationReview the plugin request handling code for $_SERVER['HTTP_ORIGIN'] or $_SERVER['HTTP_REFERER'] validation before processing admin actionsAffected if No origin/referer header validation is implemented
Your environment is affected if the WP-Cache.Com plugin versions 1.1.1 or lower is installed, active, and lacks CSRF token validation on its administrative forms and AJAX endpoints.
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 dataImplement WordPress nonces (anti-CSRF tokens) on all state-changing operations including plugin settings forms and AJAX endpoints, and validate Origin/Referer headers to ensure requests originate from legitimate sources.
Fix this in Wp Cachecom
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34177 — 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-2023-34177 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