EbookmetaApplication · Dnkorpushov

CVE-2024-36827

HIGH · 7.5 CVSS v3.1 Published 2024-06-07
Fix available
A fix is available. Upgrade to 1.2.8 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An XML External Entity (XXE) vulnerability in the ebookmeta.get_metadata function of ebookmeta before v1.2.8 allows attackers to access sensitive information or cause a Denial of Service (DoS) via crafted XML input.

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 · high confidence

The ebookmeta.get_metadata function in ebookmeta versions before v1.2.8 processes XML input (likely from ebook file formats like EPUB) without proper sanitization, allowing XML External Entity (XXE) injection. Attackers can craft malicious XML that references external entities to read local files from the server filesystem or cause Denial of Service through recursive entity expansion attacks.

MitigationUpdate ebookmeta to version 1.2.8 or later, which contains the XXE fix. Alternatively, if updating is not immediately possible, configure XML parsers to disable external entity processing and doctype declarations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EbookmetaApplication
Affected:< 1.2.8

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify ebookmeta installation
    Run 'pip show ebookmeta' or check your project's requirements.txt/dependencies for the ebookmeta package
    Affected if ebookmeta is present and the version is below 1.2.8
  2. Verify the vulnerable function usage
    Search your codebase for calls to ebookmeta.get_metadata function, particularly with input from EPUB files or other XML-containing ebook formats
    Affected if Your code calls get_metadata on untrusted EPUB or XML input files
  3. Inspect XML processing behavior
    Monitor or review how ebookmeta parses XML within EPUB files - check if external entity processing is enabled in the XML parser being used
    Affected if The XML parser allows external entity resolution or doctype declarations when processing ebook metadata
  4. Test for XXE vulnerability
    Create a minimal test EPUB with a malicious XML metadata file containing an external entity reference (e.g., <!ENTITY xxe SYSTEM "file:///etc/passwd">) and run get_metadata on it
    Affected if The function returns content from external files or experiences denial of service from recursive entity expansion

You are affected if ebookmeta version is below 1.2.8 and your application processes EPUB or other XML-based ebook files through the get_metadata function with untrusted input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 1.2.8 or later
Fixed in 1.2.8
Interim mitigation

Update ebookmeta to version 1.2.8 or later, which contains the XXE fix. Alternatively, if updating is not immediately possible, configure XML parsers to disable external entity processing and doctype declarations.

Recommended fix High confidence

1.2.8

  1. Check the currently installed version of ebookmeta using pip show ebookmeta or your package manager
  2. Upgrade ebookmeta to version 1.2.8 or later using: pip install ebookmeta>=1.2.8
  3. Verify the new version is installed correctly using pip show ebookmeta
  4. If applicable, test that the ebookmeta.get_metadata function works correctly with your existing workflows

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ebookmeta Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36827 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-36827 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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