dbcve.org
Ht Easy Ga4WordPress extension · Hasthemes

CVE-2024-1176

MEDIUM · 5.3 CVSS v3.1 Published 2024-03-13
Fix available
A fix is available. Upgrade to 1.2.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The HT Easy GA4 – Google Analytics WordPress Plugin plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the login() function in all versions up to, and including, 1.1.5. This makes it possible for unauthenticated attackers to update the email associated through the plugin with GA4.

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 confidence

The HT Easy GA4 WordPress plugin has a broken access control vulnerability in its login() function, which lacks a proper capability check. This allows unauthenticated attackers to make arbitrary changes to the GA4 email configuration stored by the plugin.

MitigationUpdate to version 1.1.6 or later which should contain the fix. If no update is available, add a capability check (e.g., current_user_can('manage_options')) to the login() function to restrict access to administrators only.

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
Ht Easy Ga4WordPress extension
Affected:< 1.2.0

CVSS 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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check the installed HT Easy GA4 plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find 'Ht Easy Ga4' by Hasthemes, and note the version number. Alternatively, inspect the main plugin file (usually ht-easy-ga4.php in wp-content/plugins/ht-easy-ga4/) and look for the 'Version' header comment.
    Affected if The installed version is lower than 1.2.0 (for example, 1.1.5, 1.1.0, or earlier)
  2. Locate the login() function in the plugin
    Search the plugin directory for the function definition 'function login()' or 'function ht_eg_login()' in the main plugin PHP files.
    Affected if The login() function exists in the plugin code (this function handles GA4 email configuration updates)
  3. Inspect the login() function for capability checks
    Open the file containing the login() function and examine its code. Look for a capability check such as 'current_user_can('manage_options')' or similar at the function start.
    Affected if The login() function does NOT contain a capability check (current_user_can) or the check is missing/insufficient, allowing any visitor to access it
  4. Test unauthenticated access to the login function
    If the site allows external access, check if the login function can be triggered via an HTTP request to the plugin endpoint without logging in. This may be a POST request to wp-admin/admin-ajax.php or similar, depending on how the function is hooked.
    Affected if Unauthenticated (not logged in) requests can reach and execute the login() function, allowing modification of GA4 email settings

You are affected if the HT Easy GA4 plugin version is below 1.2.0 AND the login() function lacks a capability check, allowing unauthenticated attackers to modify your GA4 email configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 1.2.0 or later
Fixed in 1.2.0
Interim mitigation

Update to version 1.1.6 or later which should contain the fix. If no update is available, add a capability check (e.g., current_user_can('manage_options')) to the login() function to restrict access to administrators only.

Recommended fix High confidence

1.2.0 or later

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the HT Easy GA4 plugin
  4. Update the plugin to version 1.2.0 or later, or reinstall the plugin to ensure you have the fixed version
  5. Verify the update was successful by checking the plugin version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ht Easy Ga4 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1176 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1176 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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