CVE-2024-52725: SemCms v4.8 was discovered to contain a SQL injection vulnerability.
SemCms v4.8 was discovered to contain a SQL injection vulnerability. This allows an attacker to execute arbitrary code via the ldgid parameter in the SEMCMS_SeoAndTag.php component.
Security readout for executives and security teams
Plain-English summary
SemCms v4.8 has a SQL injection issue in a SEO/tag component. A successful attacker could access sensitive database information. The public record rates it medium because exploitation requires high privileges, but confidentiality impact is high if a privileged account is compromised.
Executive priority
Handle as a moderate-priority application risk. It is not confirmed as actively exploited, but it can expose sensitive database content if a privileged CMS account or admin surface is compromised.
Technical view
CVE-2024-52725 is CWE-89 SQL injection via the ldgid parameter in SEMCMS_SeoAndTag.php. CVSS 3.1 is 4.9: network reachable, low complexity, high privileges required, no user interaction, high confidentiality impact, no integrity or availability impact recorded.
Likely exposure
Exposure appears limited to organizations running SemCms v4.8, especially internet-accessible instances where privileged CMS users can reach SEMCMS_SeoAndTag.php. The CVE metadata does not provide CPEs or a complete affected product list.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Treat exploitation status as unconfirmed. The record only identifies the vulnerable parameter and component, not public weaponization or observed attacks.
Researcher notes
Evidence is thin. The CVE names SemCms v4.8 and ldgid in SEMCMS_SeoAndTag.php, but affected CPEs, patch status, and exploit observations are absent. The description says arbitrary code execution, while CVSS records confidentiality-only impact.
Mitigation direction
Check the SemCms project or vendor guidance for a fixed release or official workaround.
Upgrade SemCms if an official patched version is available.
Restrict access to SEO/tag administration paths to trusted administrators and networks.
Reduce database account privileges used by the CMS wherever operationally feasible.
Monitor for abnormal requests or database errors involving the ldgid parameter.
Validation and detection
Inventory public and internal systems for SemCms v4.8 installations.
Confirm whether SEMCMS_SeoAndTag.php is present and reachable.
Review access controls for privileged CMS functions tied to SEO or tag management.
Check application and database logs for unusual ldgid values or SQL errors.
Track the referenced GitHub project and CVE record for patch clarification.
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.
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.