Subscriber-level license-key modification via unchecked check_license functions
Published May 20, 2023 · Updated Apr 8, 2026
Missing authorization in Groundhogg 2.7.9.8 and earlier allows remote authenticated users to replace stored license keys. The check_license functions update the license and support-license settings without checking the caller's WordPress capability. Subscriber-level access is sufficient, and each replacement must be a valid license key, limiting the impact to unauthorized license-setting changes.
Summary
What happened
Missing authorization in Groundhogg 2.7.9.8 and earlier allows remote authenticated users to replace stored license keys. The check_license functions update the license and support-license settings without checking the caller's WordPress capability. Subscriber-level access is sufficient, and each replacement must be a valid license key, limiting the impact to unauthorized license-setting changes.
The record
- CVE
- CVE-2023-2714
- Published
- May 20, 2023
- Updated
- Apr 8, 2026
- Vendor
- Groundhogg Inc.
- Product
- Groundhogg
- Classifications
- CWE-862, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 20, 2023CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.7.9.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo