Handl Utm GrabberWordPress extension · Haktansuren
CVE-2019-15769
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 handl-utm-grabber plugin before 2.6.5 for WordPress has CSRF via add_option and update_option.
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 handl-utm-grabber WordPress plugin before version 2.6.5 contains a Cross-Site Request Forgery (CSRF) vulnerability in its add_option and update_option functions. This allows attackers to trick authenticated administrators into unknowingly modifying plugin settings by luring them to visit malicious pages while logged in.
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
Handl Utm GrabberWordPress extension
< 2.6.5CVSS 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.
-
Locate the handl-utm-grabber plugin installationCheck your WordPress plugins directory (wp-content/plugins/) for a folder named 'handl-utm-grabber' or 'handl-utm-grabber-master'. Also check via WordPress admin under Plugins > Installed Plugins.Affected if The plugin folder exists in the plugins directory or appears in the WordPress admin plugins list.
-
Determine the installed plugin versionIf the plugin is installed, open the main plugin PHP file (usually handl-utm-grabber.php or similar in the plugin folder) and look for the version comment or 'Version:' header in the file header. Alternatively, check the version displayed in WordPress admin under Plugins > Installed Plugins.Affected if The version number found is less than 2.6.5 (for example, 2.6.4, 2.6.0, 1.x.x, etc.).
-
Verify the plugin is activeLog into WordPress admin and check if handl-utm-grabber appears in the active plugins list, or query the database table wp_options for the option_name 'active_plugins' to see if the plugin is included.Affected if The plugin is both installed and active on the site.
-
Confirm the vulnerable functions exist in the codeIf you have file access, open the main plugin PHP file and search for occurrences of 'add_option' and 'update_option' function calls. These functions are vulnerable if they lack nonce verification (check for missing 'wp_verify_nonce' or 'check_admin_referer' calls nearby).Affected if The plugin uses add_option or update_option functions without proper nonce validation in the code, and the version is below 2.6.5.
You are affected if the handl-utm-grabber plugin is installed, active, and its version is below 2.6.5, as this version range contains the CSRF vulnerability in the add_option and update_option functions.
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 data2.6.5
Update the handl-utm-grabber plugin to version 2.6.5 or later to patch the CSRF vulnerability. As a temporary measure, disable the plugin until the update can be applied.
Fix this in Handl Utm Grabber
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15769 — 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-15769 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