dbcve.org
Applicant ProgrammeApplication · Moj

CVE-2023-32639

MEDIUM · 5.5 CVSS v3.1 Published 2023-07-25
Fix available
A fix is available. Upgrade to after 7.06 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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
Applicant Programme Ver.7.06 and earlier improperly restricts XML external entity references (XXE). By processing a specially crafted XML file, arbitrary files on the system may be read by an attacker.

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

Applicant Programme versions 7.06 and earlier contain an XXE vulnerability where the XML parser does not properly restrict external entity references. When a user uploads or processes a specially crafted XML file, the parser resolves the external entities, allowing the attacker to read arbitrary files from the server's filesystem.

MitigationDisable external entity resolution in the XML parser configuration and implement input validation for XML uploads. Consider using a safer XML parser that has XXE protection enabled by default.

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
Applicant ProgrammeApplication
Affected:<= 7.06

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 installed version of Moj Applicant Programme
    Locate the application version information in the software (typically in About section, admin panel, or version file)
    Affected if Installed version is 7.06 or earlier
  2. Confirm XML upload or processing feature is in use
    Check if the application accepts or processes XML file uploads, or if XML data is submitted through any forms or APIs
    Affected if XML upload or processing functionality is enabled and accessible to users
  3. Inspect XML parser configuration
    Examine the application's XML parser settings or configuration files for external entity resolution settings
    Affected if External entity resolution is not explicitly disabled or restricted in the XML parser configuration

A user is affected if they are running Moj Applicant Programme version 7.06 or earlier AND the XML upload/processing feature is enabled AND the XML parser allows external entity resolution.

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.

From vendor data
Upgrade available Upgrade to a release after 7.06
Interim mitigation

Disable external entity resolution in the XML parser configuration and implement input validation for XML uploads. Consider using a safer XML parser that has XXE protection enabled by default.

Fix this in Applicant Programme Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
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,592.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32639 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2023-32639 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