CVE-2015-5632
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 · uneditedThe runtime engine in the Newphoria applican framework before 1.12.3 for Android and before 1.12.2 for iOS allows attackers to bypass a whitelist.xml URL whitelist protection mechanism and obtain API access via unspecified vectors.
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 confidenceThe Newphoria applican framework for Android and iOS contains a security flaw in its URL whitelist validation mechanism defined in whitelist.xml. Attackers can bypass this protection to make unauthorized API calls, accessing backend services that should be restricted by the whitelist policy.
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<= 1.12.1<= 1.12.2CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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.
-
Identify if the application uses the Newphoria Applican frameworkReview the application's dependencies, libraries, or bundled frameworks to determine if Newphoria Applican is included. Look for Applican-related SDK files, libraries, or package references in the application codebase.Affected if Newphoria Applican framework is present in the application
-
Determine the installed Applican version for AndroidLocate and inspect the Applican library version in the Android application build (such as in build configuration, bundled JAR files, or SDK version metadata). Compare the version number against the affected range.Affected if The Android Applican version is 1.12.1 or earlier
-
Determine the installed Applican version for iOSLocate and inspect the Applican library version in the iOS application (such as in linked frameworks, pod dependencies, or SDK version metadata). Compare the version number against the affected range.Affected if The iOS Applican version is 1.12.2 or earlier
-
Verify the whitelist.xml URL validation is in useSearch the application resources or configuration files for whitelist.xml. Confirm that the application logic references this file for URL validation or API access control decisions.Affected if whitelist.xml exists and is used as the URL whitelist validation mechanism
The environment is affected if Newphoria Applican is present with Android version 1.12.1 or earlier, or iOS version 1.12.2 or earlier, and the application relies on whitelist.xml for URL validation.
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 dataUpgrade the Newphoria applican framework to version 1.12.3 or later for Android, and version 1.12.2 or later for iOS. Review application logic that relies on the whitelist for security decisions.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5632 — 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-2015-5632 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