CVE-2024-13190
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability classified as critical was found in ZeroWdd myblog 1.0. This vulnerability affects unknown code of the file src/main/resources/mapper/BlogMapper.xml. The manipulation of the argument findBlogList/getTotalBlogs leads to xml injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceXML injection vulnerability in ZeroWdd myblog 1.0's BlogMapper.xml file where the findBlogList and getTotalBlogs parameters are not properly sanitized, allowing injection of malicious XML content through user-controlled input.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm ZeroWdd myblog versionLocate and inspect version information for the myblog application (check pom.xml, build files, or application metadata)Affected if Running version 1.0 of ZeroWdd myblog
-
Locate BlogMapper.xml fileSearch for the BlogMapper.xml file in the application's source code or deployment directory (typically in a mybatis or mapper resources folder)Affected if The BlogMapper.xml file exists and contains findBlogList and getTotalBlogs query definitions
-
Inspect findBlogList query definitionOpen BlogMapper.xml and examine the findBlogList SELECT/PARAMETER_TYPE declarations to see if it accepts direct parameter input without sanitizationAffected if The query uses parameter placeholders directly without visible input validation or parameterized query handling
-
Inspect getTotalBlogs query definitionOpen BlogMapper.xml and examine the getTotalBlogs query to verify it accepts user-controlled inputAffected if The getTotalBlogs parameter handling accepts raw user input without validation
-
Trace user input flow to XML mapperReview the service/controller layer code that calls findBlogList and getTotalBlogs to confirm user-supplied parameters are passed directly to the XML mapper without sanitizationAffected if User request parameters (GET/POST) are mapped directly to the mapper queries without input validation or escaping
-
Verify MyBatis XML mapping is activeConfirm the application uses MyBatis with XML mappers (check configuration and dependencies)Affected if The application uses MyBatis XML mappers and the vulnerable BlogMapper.xml is loaded at runtime
You are affected if running ZeroWdd myblog 1.0 where user input flows directly to the findBlogList or getTotalBlogs parameters in BlogMapper.xml without sanitization or parameterized query handling.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper input validation on parameters passed to the mapper and use MyBatis parameterized queries/prepared statements to prevent XML injection, or sanitize user input before constructing XML queries.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13190 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-13190 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data