dbcve.org
E BelediyeApplication · Eskom

CVE-2023-6151

HIGH · 7.5 CVSS v3.1 Published 2023-11-28
Fix available
A fix is available. Upgrade to 105 or later.
See remediation →
84/100
Remediation priority · High
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
Incorrect Use of Privileged APIs vulnerability in ESKOM Computer e-municipality module allows Collect Data as Provided by Users. This issue affects e-municipality module: before v.105.

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

This is an API validation vulnerability in ESKOM's e-municipality module where the system accepts and processes data from users without proper validation or privilege enforcement. The incorrect use of privileged APIs allows users to submit data that should be restricted or validated, potentially enabling data injection or unauthorized data collection. The vulnerability exists in versions prior to v.105.

MitigationUpgrade the e-municipality module to version 105 or later, which contains the fix for proper input validation and privileged API usage. If immediate patching is not possible, implement input validation and authorization checks at the API layer to ensure user-submitted data is properly sanitized and access controls are enforced.

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
E BelediyeApplication
Affected:< 105

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 checks

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

  1. Identify if Eskom E Belediye is deployed
    Locate and confirm the presence of the Eskom E Belediye application in your environment, typically found in the web application directory or application server.
    Affected if The application is present and accessible in your environment.
  2. Determine installed version
    Access the application administration panel, check the About section, or examine the application metadata files to identify the exact version number.
    Affected if The version is below 105 (e.g., 104, 103, 102, etc.).
  3. Verify e-municipality module is active
    Confirm the e-municipality module is enabled and accessible within the Eskom E Belediye installation.
    Affected if The e-municipality module is loaded and operational.
  4. Check API endpoints exposure
    Identify publicly accessible API endpoints within the e-municipality module by reviewing application routing configuration or API documentation.
    Affected if API endpoints are exposed without proper authentication or validation layers.

Your environment is affected if Eskom E Belediye is running with a version below 105 and the e-municipality module is enabled with accessible API endpoints.

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 105 or later
Fixed in 105
Interim mitigation

Upgrade the e-municipality module to version 105 or later, which contains the fix for proper input validation and privileged API usage. If immediate patching is not possible, implement input validation and authorization checks at the API layer to ensure user-submitted data is properly sanitized and access controls are enforced.

Recommended fix High confidence

Upgrade to E Belediye e-municipality module version 105 or later

  1. Identify the current installed version of ESKOM Computer e-municipality (E Belediye) module
  2. Contact ESKOM Computer or your authorized vendor to obtain version 105 or later
  3. Schedule a maintenance window for the upgrade process
  4. Back up all current configurations and data of the e-municipality module
  5. Deploy version 105 of the e-municipality module following vendor-provided installation documentation
  6. Verify the upgrade was successful by checking the module version
  7. Test core functionality to ensure the upgrade did not break existing workflows
  8. Validate that the vulnerability is resolved
Caveat Review vendor release notes for any configuration or feature changes between your current version and v105; test in staging environment before production deployment

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

Fix this in E Belediye Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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