CVE-2023-31581 is a critical-severity (CVSS 9.8) Hard-coded Credentials vulnerability in com.usthe.sureness:sureness-core. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for com.usthe.sureness:sureness-core — see the affected versions and patch details below.
Sureness uses hardcoded key
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-31581.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
com.usthe.sureness:sureness-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Dromara Sureness before v1.0.8 was discovered to use a hardcoded key.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.usthe.sureness:sureness-core | all versions | 1.0.8com.usthe.sureness:sureness-core:1.0.8 |
Affected Products
surenessdromaraResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.usthe.sureness:sureness-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.usthe.sureness:sureness-core to 1.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-31581 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2023-31581 in your dependencies?
Find it across Maven, including transitive dependencies.