Secuno
ENNL
Book demo

CVE-2024-28714

Crmeb Java remote code execution

8.1 HIGHPublic exploitEPSS 0.85%
  1. Published28 Mar 2024

Description

SQL Injection vulnerability in CRMEB_Java e-commerce system v.1.3.4 allows an attacker to execute arbitrary code via the groupid parameter.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredLow
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected products

Crmeb Java< 1.3.4

Remediation

Fixed in
Crmeb Java≥ 1.3.4

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-891138.8
SAP Commerce Cloud does not sufficiently validate certain user-supplied input before it…
CVE-2026-1096088.8
Frappe ERPNext before 15.121.0 and 16.x before 16.34.0 contains an SQL injection…
CVE-2026-1095738.1
phpMyFAQ before 4.1.9 contains an SQL injection vulnerability in PdoMysql::escape(),…
CVE-2026-893028.6
The Post Voting System WordPress plugin through 1.0 does not properly sanitize and…
CVE-2026-892998.6
The WP Verify API WordPress plugin through 1.0.0 does not properly sanitize and escape…
CVE-2026-892978.6
The Loja Automática WordPress plugin through 1.0.0 does not properly sanitize and…

Frequently asked

Is CVE-2024-28714 being actively exploited?

CVE-2024-28714 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.85%.

How severe is CVE-2024-28714?

CVE-2024-28714 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 0.85% probability of exploitation.

Which products are affected by CVE-2024-28714?

Affected products include Crmeb Java.

How do I fix CVE-2024-28714?

Upgrade affected software to a fixed version, for example Crmeb Java 1.3.4 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-28714 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.