CVE-2024-46532: SQL Injection vulnerability in OpenHIS v.1.0 allows an attacker to execute arbitrary code via the refund fu...
SQL Injection vulnerability in OpenHIS v.1.0 allows an attacker to execute arbitrary code via the refund function in the PayController.class.php component.
Security readout for executives and security teams
Plain-English summary
CVE-2024-46532 is a critical SQL injection issue reported in OpenHIS v1.0. The vulnerable area is the refund function in PayController.class.php. If exposed, an unauthenticated network attacker may affect confidentiality, integrity, and availability. The available sources do not name a vendor patch or confirm active exploitation.
Executive priority
Treat this as urgent if OpenHIS v1.0 is in production or internet-accessible. The potential impact is high across data confidentiality, integrity, and availability. If OpenHIS is not present, document non-exposure and continue monitoring for updated vendor information.
Technical view
The CVE describes CWE-89 SQL injection in OpenHIS v1.0, specifically the refund function of PayController.class.php. It carries CVSS 3.1 score 9.8 with network access, low complexity, no privileges, and no user interaction. The record states potential arbitrary code execution, but source detail is limited.
Likely exposure
Organizations running OpenHIS v1.0 are the likely exposed group, especially if the application is reachable from untrusted networks. The CVE data does not provide CPEs, vendor identifiers, deployment scope, or affected version ranges beyond OpenHIS v1.0.
Exploitation context
The CVE is not listed as KEV in the provided bundle, so active exploitation is not established here. A public GitHub reference exists for CVE-2024-46532, but this analysis does not rely on or reproduce exploit procedure details.
Researcher notes
The public CVE metadata is sparse: affected vendor/product fields are listed as n/a, and no official patch is named. The strongest grounded facts are OpenHIS v1.0, PayController.class.php refund function, CWE-89, CVSS 9.8, and non-KEV status in the provided data.
Mitigation direction
Identify whether OpenHIS v1.0 is deployed in your environment.
Check the OpenHIS project and CVE references for vendor remediation guidance.
Restrict untrusted network access to affected OpenHIS instances.
If feasible, limit use of the refund function until remediated.
Increase monitoring for database errors and suspicious refund-related activity.
Back up application data and database contents before remediation work.
Validation and detection
Confirm application name and version from deployment records.
Verify whether PayController.class.php exists in the deployed codebase.
Review whether the refund function is enabled or externally reachable.
Review logs for unusual refund requests or SQL error patterns.
Use authorized security testing to assess SQL injection exposure safely.
Track the CVE record for updated affected-version or fix information.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.