Woocommerce Address BookWordPress extension · Hallme
CVE-2019-15770
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 · uneditedThe woo-address-book plugin before 1.6.0 for WordPress has save calls without nonce verification checks.
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 confidenceThe woo-address-book WordPress plugin before version 1.6.0 contains Cross-Site Request Forgery (CSRF) vulnerabilities due to missing nonce verification on save operations. This allows attackers to trick authenticated administrators into unknowingly submitting crafted requests that modify plugin data.
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
Woocommerce Address BookWordPress extension
< 1.6.0CVSS 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 the plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WooCommerce Address Book' or 'Hallme Woocommerce Address Book' in the listAffected if The plugin appears in the installed plugins list
-
Check the installed versionOn the Plugins page, locate the woo-address-book plugin and note the version number displayed below the plugin nameAffected if The version shown is below 1.6.0 (for example, 1.5.x, 1.4.x, etc.)
-
Confirm the plugin is activeOn the Plugins page, verify that the plugin has an 'Active' status indicator under the plugin nameAffected if The plugin is active and the version is below 1.6.0
-
Inspect save operation code for nonce verification (optional deeper check)Access the plugin files via FTP or file manager, navigate to the plugin directory, and examine the PHP files handling save operations (typically files with 'save' in the name or form handlers) to verify if they include nonce verification using wp_verify_nonce or check_admin_refererAffected if The code handling save operations lacks proper nonce verification and the plugin version is below 1.6.0
A user is affected if the Hallme Woocommerce Address Book plugin is installed, active, and running at a version lower than 1.6.0, as this version range contains the CSRF vulnerability due to missing nonce verification on save operations.
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 data1.6.0
Update the woo-address-book plugin to version 1.6.0 or later, which includes proper nonce verification checks on all save operations.
Fix this in Woocommerce Address Book
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15770 — 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-15770 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