Personalized Woocommerce Cart PageWordPress extension · Najeebmedia
CVE-2019-5979
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 Personalized WooCommerce Cart Page 2.4 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 · moderate confidenceCSRF vulnerability in the Personalized WooCommerce Cart Page WordPress plugin (versions 2.4 and earlier) allows remote attackers to forge requests that hijack administrator authentication. The attacker tricks an authenticated admin into visiting a malicious site or clicking a crafted link, causing the browser to send unintended requests to the vulnerable plugin with the admin's session credentials.
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
Personalized Woocommerce Cart PageWordPress extension
<= 2.4CVSS 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.
-
Confirm plugin is installedAccess WordPress admin dashboard and go to Plugins > Installed Plugins. Look for 'Personalized WooCommerce Cart Page' by Najeebmedia. Alternatively, check the wp-content/plugins/ directory for a folder containing 'najeebmedia' and 'personalized-cart' in the name.Affected if The plugin appears in the list of installed WordPress plugins
-
Identify installed versionIn the Plugins list, find the 'Personalized WooCommerce Cart Page' entry and read the version number displayed beneath the plugin name. Alternatively, open the main plugin PHP file (usually named like personalized-woocommerce-cart-page.php) and look for the 'Version:' header comment in the file metadata.Affected if The displayed version is 2.4 or lower
-
Verify vulnerable version rangeCompare the identified version number against the affected version range: any version up to and including 2.4 is vulnerable.Affected if The installed version is 2.4 or any earlier version number
-
Confirm admin access existsVerify that the WordPress site has an administrator account logged in or that administrator sessions are active, since the CSRF attack requires a logged-in admin to trigger the forged request.Affected if The site has active administrator authentication that could be exploited via crafted links
If the Personalized WooCommerce Cart Page plugin is installed and the version is 2.4 or lower, the environment is vulnerable to CVE-2019-5979 CSRF attacks.
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 the plugin to the latest version to receive the vendor patch. If no update is available, implement anti-CSRF tokens on all state-changing admin actions and validate request Origin/Referer headers.
Fix this in Personalized Woocommerce Cart Page
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-5979 — 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-5979 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