CVE-2024-29470: DBlog · Cross-site Scripting
Affects DBlogSource CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Mar 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubyadong.zhang/DBlogpkg:github/yadong.zhang/DBlogOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Implement strict input validation and sanitization on all user-supplied data, especially in the {{rootpath}}/links component, to prevent malicious script injection.
- Apply output encoding or escaping techniques when rendering user input in HTML contexts to neutralize any embedded scripts.
- Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers.
- Monitor web application logs for unusual input patterns or repeated attempts to inject scripts.
- Educate users about the risks of clicking on suspicious links and encourage cautious browsing behavior.
- If possible, upgrade to a patched version of OneBlog once available or apply vendor-provided patches promptly.
- Use web application firewalls (WAFs) configured to detect and block common XSS attack patterns targeting the affected component.
- Conduct regular security assessments and penetration testing focused on input validation and XSS vulnerabilities.
- Isolate critical user sessions and implement multi-factor authentication to reduce the impact of session hijacking.
- Backup website data regularly to enable recovery in case of defacement or compromise.
Description
OneBlog v2.3.4 was discovered to contain a stored cross-site scripting (XSS) vulnerability via the component {{rootpath}}/links.