Skip to main content
CVE-2024-48072VulnerabilityPublished Updated

CVE-2024-48072: ecology · n/a

Affects ecologySource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 10.0.0 as a priority.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 10.0.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade weaver/ecology to 10.0.0.

Affected software

ProductAffectedFixed in
GitHubweaver/ecologypkg:github/weaver/ecologyOther threatsAffected
  • 9.0.0 <10.0.0
Fixed in
  • 10.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately restrict external access to the /mobilemode/Action.jsp endpoint, ideally limiting it to trusted internal networks or VPN users only. 2. Implement Web Application Firewall (WAF) rules to detect and block SQL injection patterns targeting the vulnerable parameters, especially 'searchField' and 'whereClause'. 3. Conduct thorough input validation and sanitization on all user-supplied parameters in the affected component, employing parameterized queries or prepared statements to prevent SQL injection. 4. Monitor application logs and network traffic for unusual or suspicious requests targeting the vulnerable endpoint. 5. 6. Consider deploying database activity monitoring solutions to detect anomalous queries indicative of exploitation attempts. 7. Educate relevant IT and security staff about the vulnerability and ensure incident response plans are updated to address potential exploitation scenarios. 8. If feasible, isolate affected systems until a patch is applied to minimize risk exposure.

Description

Weaver Ecology v9.* was discovered to contain a SQL injection vulnerability via the component /mobilemode/Action.jsp?invoker=com.weaver.formmodel.mobile.mec.servlet.MECAction&action=getFieldTriggerValue&searchField=*&fromTable=HrmResourceManager&whereClause=1%3d1&triggerCondition=1&expression=%3d&fieldValue=1.

References

Community reviews

Loading reviews…