dbcve.org
GoloWordPress extension · Uxper

CVE-2024-12876

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-07
Fix available
A fix is available. Upgrade to 1.6.11 or later.
See remediation →
100/100
Remediation priority · Urgent
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 Golo - City Travel Guide WordPress Theme theme for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 1.6.10. This is due to the plugin not properly validating a user's identity prior to updating their password. This makes it possible for unauthenticated attackers to change arbitrary user's passwords, including administrators, and leverage that to gain access to their account.

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 Golo WordPress theme fails to validate user identity before processing password reset requests, allowing unauthenticated attackers to supply arbitrary user identifiers (such as usernames or email addresses) and set new passwords for those accounts. This enables complete administrative account takeover without any credentials.

MitigationUpdate the Golo theme to version 1.6.11 or later where the vulnerability is patched. If immediate update is not possible, restrict access to password reset endpoints via web server rules or temporarily disable the theme.

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
GoloWordPress extension
Affected:< 1.6.11

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

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

  1. Locate the Golo theme version
    In WordPress admin, go to Appearance > Themes and click on the Golo theme to view its details. Alternatively, access the theme directory via FTP or file manager and open style.css to find the Version: header.
    Affected if The reported version is lower than 1.6.11 (for example, 1.6.10, 1.6.9, etc.)
  2. Confirm theme name matches affected product
    Verify that the installed theme is specifically 'Uxper Golo' or 'Golo - City Travel Guide' and not a similarly named theme.
    Affected if The theme name is Golo by Uxper and the version is below 1.6.11
  3. Review admin user accounts for unauthorized changes
    In WordPress admin, go to Users > All Users and examine the list of administrator accounts. Check the 'Last Login' column (if available via plugin) or review user registration dates and email addresses for unfamiliar accounts.
    Affected if New or unexpected administrator accounts exist, or existing admin accounts have changed email addresses or passwords that you did not initiate
  4. Check for password reset activity
    If your WordPress has audit logging plugins or server access logs, search for POST requests to /wp-login.php?action=lostpassword or REST API password reset endpoints from unfamiliar IP addresses.
    Affected if Password reset requests or account changes occurred from IPs you do not recognize, especially in bulk or automated patterns

You are affected if the Golo theme version is below 1.6.11 and you have not already audited or secured admin accounts after the vulnerability disclosure period.

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.6.11 or later
Fixed in 1.6.11
Interim mitigation

Update the Golo theme to version 1.6.11 or later where the vulnerability is patched. If immediate update is not possible, restrict access to password reset endpoints via web server rules or temporarily disable the theme.

Recommended fix High confidence

Golo theme version 1.6.11

  1. Update the Golo - City Travel Guide WordPress Theme to version 1.6.11 or later through WordPress admin (Appearance > Themes) or via the theme provider
  2. After updating, review all administrator-level user accounts for any unauthorized changes
  3. As a security precaution, reset passwords for all administrator accounts to ensure no compromised credentials remain

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

Fix this in Golo Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12876 — 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-12876 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