CVE-2024-38747
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 · uneditedExposure of Sensitive Information to an Unauthorized Actor vulnerability in HitPay Payment Solutions Pte Ltd HitPay Payment Gateway for WooCommerce allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects HitPay Payment Gateway for WooCommerce: from n/a through 4.1.3.
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 · moderate confidenceThe HitPay Payment Gateway for WooCommerce plugin versions up to 4.1.3 contain an access control vulnerability allowing unauthorized access to sensitive information due to functionality not properly constrained by ACLs. This allows attackers to potentially access sensitive payment-related data or perform actions outside their authorized scope.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify HitPay Payment Gateway for WooCommerce is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'HitPay Payment Gateway for WooCommerce' in the list. Note whether it is active or inactive.Affected if The plugin is installed and active, with version 4.1.3 or lower shown in the plugin details
-
Check the installed plugin versionClick on the plugin in the WordPress plugins list to view details, or check the plugin header in wp-content/plugins/hitpay-payment-gateway-for-woocommerce/hitpay-payment-gateway.php for the Version field.Affected if The version listed is 4.1.3 or any version up to and including 4.1.3
-
Identify accessible plugin endpointsCheck for publicly accessible files within the plugin directory, particularly any AJAX handlers or API files in /wp-content/plugins/hitpay-payment-gateway-for-woocommerce/ that may be accessible without authentication.Affected if AJAX or API endpoints in the plugin are accessible to unauthenticated users (no check for is_user_logged_in() or proper capability checks)
-
Review payment-related data exposureExamine server access logs for requests to HitPay plugin files from unauthenticated IP addresses. Look for patterns like /?wc-api=hitpay or direct PHP file access that should require authentication.Affected if Unauthenticated requests to payment processing endpoints return sensitive payment data or execute payment-related functions
A user is affected if the HitPay Payment Gateway for WooCommerce plugin is installed with version 4.1.3 or lower and the vulnerable access control paths are accessible to unauthenticated users.
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 dataUpdate HitPay Payment Gateway for WooCommerce to the latest version (beyond 4.1.3) to remediate the access control and information disclosure vulnerability.
- 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-2024-38747 — 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-2024-38747 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