Security readout for executives and security teams
Plain-English summary
FrontAccounting 2.4.5 has a reported SQL injection issue in an attachments page parameter. A successful attacker could infer database contents, potentially exposing financial and operational records stored in the application. Public exploit material exists, but the supplied sources do not show confirmed active exploitation.
Executive priority
Prioritize exposed FrontAccounting 2.4.5 systems because the reported impact is database extraction from a business application. Urgency is lower if the affected page is not reachable by untrusted users.
Technical view
The CVE describes time-based blind SQL injection in /attachments.php via the filterType parameter in FrontAccounting 2.4.5. The stated impact is potential extraction of the full application database. The source bundle provides no CVSS score, CWE mapping, CPEs, or named fixed version.
Likely exposure
Organizations running FrontAccounting 2.4.5 with /attachments.php reachable by untrusted users are the likely exposure. The bundle does not establish other affected versions, CPEs, or deployment types.
Exploitation context
Exploit-DB is cited, so public exploit information exists. The CVE is not listed as KEV in the supplied bundle, and no cited source confirms active exploitation in the wild.
Researcher notes
Evidence is narrow but specific: version 2.4.5, /attachments.php, filterType, time-based blind SQL injection. Missing CVSS, CWE, CPE, and fixed-version data should be called out in any advisory or ticket.
Mitigation direction
- Check FrontAccounting vendor guidance and issue #37 for the fixed version or official remediation.
- Upgrade or patch affected FrontAccounting 2.4.5 instances when vendor guidance confirms the target version.
- Restrict untrusted access to /attachments.php until remediation is complete.
- Review database and application credentials if suspicious access is found.
Validation and detection
- Inventory FrontAccounting deployments and identify any running version 2.4.5.
- Confirm whether /attachments.php is reachable from the internet or untrusted networks.
- Review application logs for suspicious filterType requests or unusual response timing patterns.
- Verify remediation against vendor guidance before returning normal access.
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.
Database 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-2018-1000890 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- 46037CVE reference · exploit, x_refsource_EXPLOIT-DB
- https://github.com/FrontAccountingERP/FA/issues/37CVE reference · x_refsource_MISC
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.