Security readout for executives and security teams
Plain-English summary
CVE-2026-1552 is a SQL injection issue in SEMCMS 5.0. A remote authenticated attacker may manipulate a search parameter to affect the database. Public exploit material is referenced, but the source bundle does not show confirmed active exploitation. Treat exposed SEMCMS 5.0 sites as a business risk, especially where customer, order, or content data is stored.
Executive priority
Prioritize within normal vulnerability remediation cycles, faster for internet-facing SEMCMS 5.0 sites holding sensitive data. Public exploit disclosure raises urgency, but authenticated access and lack of confirmed active exploitation keep this below emergency status based on available sources.
Technical view
The vulnerability affects /SEMCMS_Info.php in SEMCMS 5.0. Manipulation of the searchml argument leads to SQL injection. The CVSS v2 vector is AV:N/AC:L/Au:S/C:P/I:P/A:P with score 6.5. VulDB lists CWE-89 and CWE-74. Vendor contact reportedly received no response, and no official patch is identified in the provided sources.
Likely exposure
Exposure is likely limited to organizations running SEMCMS 5.0, especially internet-facing deployments. The CVSS vector indicates network access and low complexity, but authentication is required. Risk increases if low-privileged accounts are easy to obtain or the affected page is reachable from the internet.
Exploitation context
The exploit has been publicly disclosed according to the CVE description and linked GitHub issue. The bundle does not include CISA KEV status or another cited source confirming active exploitation. Do not assume compromise solely from version presence, but prioritize review because public proof-of-concept material lowers attacker effort.
Researcher notes
Evidence is primarily from CVE/VulDB records and a linked public issue. Affected code is described only as unknown code in /SEMCMS_Info.php. No vendor fix, patch version, or workaround is named. Avoid deriving exploit mechanics from public PoC content when validating in production.
Mitigation direction
- Identify whether SEMCMS 5.0 is deployed and internet-facing.
- Check SEMCMS vendor or project channels for official guidance or updates.
- Restrict access to SEMCMS administrative and affected pages where feasible.
- Review web application firewall rules for generic SQL injection detection.
- Back up application and database before making emergency changes.
- Consider isolating or retiring exposed SEMCMS 5.0 instances if no fix exists.
Validation and detection
- Inventory SEMCMS versions across public and internal web assets.
- Confirm whether /SEMCMS_Info.php is present and reachable.
- Review access logs for suspicious requests involving searchml.
- Check database and application logs for unusual query errors.
- Verify whether authentication is required for the affected function.
- Document compensating controls and remaining 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-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCWE-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-2026-1552 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
- Medium
- CVSS
- 6.5 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
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.
AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR86.4Primary CVE scoreVulnerability scoring details
Base CVSS 2.0 score
6.5MediumVector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Source materials
- CVE List V5 sourceCVE List V5
- VDB-343248 | SEMCMS SEMCMS_Info.php sql injectionCVE reference · vdb-entry, technical-description
- VDB-343248 | CTI Indicators (IOB, IOC, TTP, IOA)CVE reference · signature, permissions-required
- Submit #740549 | SEMCMS SEMCMS 外贸网站php多语言版 V5.0 SQL InjectionCVE reference · third-party-advisory
- https://github.com/Sqli22/Sqli/issues/4CVE reference · exploit, issue-tracking
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 in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
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.