Wp Open GraphWordPress extension · Custom4web
CVE-2019-5960
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 WP Open Graph 1.6.1 and earlier allows remote attackers to hijack the authentication of administrators via unspecified vectors.
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 confidenceCross-site request forgery (CSRF) vulnerability in the WP Open Graph WordPress plugin versions 1.6.1 and earlier allows remote attackers to execute unauthorized administrative actions by tricking logged-in administrators into visiting malicious pages. The plugin lacks proper anti-CSRF token validation on admin functions, enabling attackers to hijack administrator sessions.
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 Open GraphWordPress 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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/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 Open Graph plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Custom4web Wp Open Graph' or 'WP Open Graph' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'wp-open-graph' or similar.Affected if The plugin is present in the WordPress installation
-
Check the installed plugin versionIn WordPress admin, find the plugin in Plugins > Installed Plugins and view the version number displayed below the plugin name. Or inspect the main plugin PHP file header for the 'Version' field.Affected if Version is 1.6.1 or lower
-
Confirm the plugin is activeIn WordPress admin > Plugins > Installed Plugins, verify the plugin shows 'Active' status. CSRF attacks require an authenticated administrator session.Affected if Plugin is activated and running on the site
-
Identify admin-accessible form actionsReview plugin source code in /wp-content/plugins/ for admin-side forms (typically in admin/ subdirectory or containing 'admin' in code). Look for form tags and AJAX handlers that perform settings changes or content modifications.Affected if Plugin contains admin forms or AJAX endpoints without nonce verification
A site is affected if the WP Open Graph plugin version 1.6.1 or lower is installed and active, exposing admin functions to CSRF attacks when authenticated administrators visit malicious external pages.
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 admin-side forms and AJAX actions, and verify these nonces on form submission to prevent unauthorized requests.
Fix this in Wp Open Graph
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-2019-5960 — 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-2019-5960 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