Cyber Resilience

CVE-2025-9848

Scriptandtools Real Estate Management System 1.0

Public PoC
Published
03 September 2025
Modified
17 June 2026
CVSS Score v4 5.5
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0061 46th percentile
Risk Priority 39 floored blend · peak EPSS

Summary

CVE-2025-9848 is a medium-severity EAR (CWE-698) vulnerability in Scriptandtools Real Estate Management System. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 46th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

A security vulnerability has been detected in ScriptAndTools Real Estate Management System 1.0. The affected element is an unknown function of the file /admin/userlist.php. Such manipulation leads to execution after redirect. The attack can be executed remotely. The exploit has…

more

been disclosed publicly and may be used.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-5128Same product: Scriptandtools Real Estate Management System
CVE-2025-6329Same product: Scriptandtools Real Estate Management System
CVE-2025-9847Same product: Scriptandtools Real Estate Management System
CVE-2026-3264Shared CWE-698, CWE-705
CVE-2026-3262Shared CWE-698, CWE-705
CVE-2026-10271Shared CWE-698, CWE-705
CVE-2025-3557Same vendor: Scriptandtools
CVE-2025-4067Same vendor: Scriptandtools
CVE-2025-4065Same vendor: Scriptandtools
CVE-2025-4066Same vendor: Scriptandtools

Affected Assets

scriptandtools
real estate management system
1.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover execution paths that continue after a redirect.

Proper access enforcement reduces the impact of continued execution after a redirect by limiting what the remaining code can do.

Requiring a documented secure development process and standards can mandate exiting immediately after issuing redirects.

Security engineering principles can require structured control-flow constructs and explicit state transitions that avoid improper scoping after tasks or errors.

Failing to a known state on indicated failures limits damage from control-flow errors without preventing the underlying scoping mistake.

Fail-safe procedures reduce the consequences of unhandled or mis-scoped control flow on failure but do not correct the scoping defect itself.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent improper redirect handling via code review and static analysis, but eliminating only this flaw covers a narrow slice of the control's broader intent.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect EAR flaws before deployment.

prevents

Secure development lifecycle requires proper handling of redirects and exit logic, reducing EAR risk.

prevents

Application security requirements can mandate safe redirect patterns and post-redirect termination.

prevents

Secure architecture principles discourage continued execution after redirects.

prevents

Secure coding standards directly address proper redirect handling and flow termination.

References