Security readout for executives and security teams
Plain-English summary
Selfwealth iOS mobile App 3.3.1 reportedly exposed hardcoded API keys. If those keys remained valid, someone could use them outside the app and access protected data tied to the key permissions. The sources do not identify a fixed version or vendor remediation.
Executive priority
Treat this as a high-priority credential exposure if your organization operates or integrates with affected Selfwealth services. Business urgency depends on whether the exposed keys are still active and what data they can access.
Technical view
CVE-2023-23132 is a CWE-798 hardcoded credential issue in Selfwealth iOS mobile App 3.3.1. The CVSS 3.1 score is 7.5, driven by network reachability, no authentication, no user interaction, and high confidentiality impact. Public metadata does not define CPEs or affected vendor fields.
Likely exposure
Exposure is most likely where Selfwealth iOS mobile App 3.3.1 was installed, archived, tested, or distributed, and where backend APIs accepted the embedded keys. The source bundle does not provide CPEs, exact backend services, or key scope.
Exploitation context
The bundle marks this CVE as not in KEV, and no cited source confirms active exploitation. A public GitHub reference exists for the disclosure, but the provided evidence does not prove real-world abuse.
Researcher notes
Public metadata is sparse: affected vendor/product fields are n/a, no CPEs are supplied, and no patch is named. Scope should be confirmed through the CVE record, the linked GitHub disclosure, vendor communication, and internal key-management evidence.
Mitigation direction
- Check vendor or Selfwealth guidance for a corrected app version.
- Revoke and rotate any API keys exposed in affected app builds.
- Audit backend permissions tied to the disclosed keys.
- Monitor API logs for unusual use of affected credentials.
- Remove hardcoded secrets from mobile builds if you maintain the app.
Validation and detection
- Confirm whether Selfwealth iOS mobile App 3.3.1 exists in your inventory.
- Review mobile app security scan results for hardcoded API keys.
- Verify exposed keys are disabled or rotated in backend systems.
- Check logs for unexpected use of the affected key identities.
- Document vendor response, fixed version status, and residual exposure.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-798: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-23132 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/l00neyhacker/CVE-2023-23132CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Hard-coded Credentials
Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.