dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-15482

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Chapa Payment Gateway Plugin for WooCommerce plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.0.3 via 'chapa_proceed' WooCommerce API endpoint. This makes it possible for unauthenticated attackers to extract sensitive data including the merchant's Chapa secret API key.

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 confidence

The Chapa Payment Gateway Plugin for WooCommerce exposes a sensitive API endpoint ('chapa_proceed') that lacks proper authentication controls, allowing unauthenticated attackers to retrieve the merchant's Chapa secret API key through direct API calls.

MitigationUpdate the plugin to a patched version beyond 1.0.3 that implements proper authentication and authorization checks on the 'chapa_proceed' endpoint, and rotate any exposed API keys immediately.

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
Low
Integrity
None
Availability
None

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

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

  1. Verify WooCommerce is installed
    Check your WordPress plugins page or inspect the wp-content/plugins directory for WooCommerce
    Affected if WooCommerce must be present for the Chapa plugin to be exploitable
  2. Identify Chapa Payment Gateway plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins, locate 'Chapa Payment Gateway for WooCommerce' and note the version number displayed
    Affected if Plugin versions 1.0.3 and earlier contain the vulnerability; versions beyond 1.0.3 are patched
  3. Confirm the vulnerable endpoint exists
    Access the URL endpoint /?wc-api=chapa_proceed or /wp-json/chapa/v1/proceed on your site using a browser or curl without providing any authentication credentials
    Affected if If the endpoint loads without requiring authentication, the vulnerability is present
  4. Check if Chapa API key is configured
    Go to WooCommerce > Settings > Payments > Chapa, or inspect the wp_options table for option_name containing 'chapa' and 'secret_key'
    Affected if If a Chapa secret API key is stored and the endpoint is accessible without auth, the key is at risk of exposure

Your environment is affected if the Chapa Payment Gateway plugin version is 1.0.3 or earlier AND the /chapa_proceed endpoint responds to unauthenticated requests, exposing your stored Chapa secret API key.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a patched version beyond 1.0.3 that implements proper authentication and authorization checks on the 'chapa_proceed' endpoint, and rotate any exposed API keys immediately.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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