Security readout for executives and security teams
Plain-English summary
Obi08 Enrollment System 1.0 has an unauthenticated SQL injection flaw in /get_subject.php. A remote attacker could query the database and expose sensitive user information, including usernames and passwords. The supplied CVSS 4.0 score is 8.7, reflecting high confidentiality risk without required credentials or user interaction.
Executive priority
Prioritize promptly if version 1.0 is deployed or externally reachable. The vulnerability requires no authentication and may expose account credentials, creating follow-on access risk. Immediate inventory and containment are warranted; emergency incident escalation should depend on evidence of attempted access or data exposure.
Technical view
CVE-2024-58276 is CWE-89 in the keyword parameter of /get_subject.php. The supplied record describes UNION-based extraction from the users table. The vector indicates network reachability, low complexity, no prerequisites, privileges, or user interaction, and high vulnerable-system confidentiality impact. The title mentions login.php, conflicting with the described endpoint.
Likely exposure
Exposure is most likely where Obi08 Enrollment System 1.0 is deployed and /get_subject.php is reachable by untrusted users, especially over the internet. The bundle identifies no other affected versions or products. Actual deployment prevalence, default exposure, and patch status are not established by the supplied sources.
Exploitation context
A public ExploitDB entry is referenced, showing that exploitation information is publicly available. However, the CVE is not listed as KEV in the supplied bundle, and no cited evidence establishes active exploitation in the wild. Treat attempts as plausible, not confirmed.
Researcher notes
The supplied title identifies login.php, while the description and technical details identify /get_subject.php and its keyword parameter. Validate against the CVE record and advisory before building detection logic. No vendor patch, fixed version, or official mitigation is identified in the bundle. Public exploit material exists, but active exploitation is unconfirmed.
Mitigation direction
- Identify and prioritize every deployment of Obi08 Enrollment System 1.0.
- Check the project and advisory sources for current vendor remediation guidance.
- Restrict untrusted access to the affected endpoint until supported remediation is confirmed.
- Preserve relevant application, web-server, and database logs for investigation.
- Rotate exposed credentials if investigation indicates database access or disclosure.
Validation and detection
- Confirm the installed product and version on every suspected deployment.
- Determine whether /get_subject.php is reachable without authentication from untrusted networks.
- Review logs for anomalous keyword requests and unexpected database query patterns.
- Assess whether user records or credentials may have been accessed.
- After remediation, verify untrusted input cannot alter the endpoint's database query structure.
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-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.
Open ATT&CK lookupDatabase behavior lookup
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.
Open ATT&CK lookupCVE-2024-58276 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
- 8.7 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA: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.
SSVC decision data
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:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-51845CVE reference, VulnCheck · exploit
- Official Product HomepageCVE reference, VulnCheck · product
- https://www.vulncheck.com/advisories/obi08-enrollment-system-10-loginphp-sql-injectionCVE reference, VulnCheck · third-party-advisory
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.
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.