Secuno
ENNL
Book demo

CVE-2024-48907

Sematell Replyone server-side request forgery (SSRF)

7.5 HIGHPublic exploitEPSS 0.44%
  1. Published1 May 2025

Description

Sematell ReplyOne 7.4.3.0 allows SSRF via the application server API.

CVSS 3.1 breakdown

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

Affected products

Sematell Replyone7.4.3.0

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-8911110.0
The SAP Cloud SDK for Python contains an OAuth2 SSRF vulnerability affecting…
CVE-2026-571438.8
PraisonAI is a multi-agent teams system. Prior to praisonaiagents 1.6.62,…
CVE-2026-1092388.6
Crawl4AI 0.7.0 before 0.9.4 contains a server-side request forgery vulnerability that…
CVE-2026-859528.5
Affected Linux-based Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x…
CVE-2026-859518.5
Progress MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7…
CVE-2026-694359.6
Missing authorization in Azure SRE Agent allows an authorized attacker to elevate…

Frequently asked

Is CVE-2024-48907 being actively exploited?

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

How severe is CVE-2024-48907?

CVE-2024-48907 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.44% probability of exploitation.

Which products are affected by CVE-2024-48907?

Affected products include Sematell Replyone.

How do I fix CVE-2024-48907?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-48907 against the real software inventory on every managed device, every day. 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.