CVE-2017-1002003

Public exploit available. Not confirmed exploited in the wild yet. Fixed in 1.1.4.

CVSS 3.09.8Critical EPSS percentile96th12% chance in 30 days CISA KEVNot listedNo confirmed exploitation
Public exploit: 1 source Fix1.1.4Upgrade to this build

Published 2017-09-14Updated 2026-05-13Sources: CVE.org, NVD

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

Invedion Wp2android-turn-wp-site-into-android-appAffected: ≥ unspecified, < 1.1.4Upgrade to: 1.1.4Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record

In your WordPress admin area, check the installed plugin version for “wp2android-turn-wp-site-into-android-app”.
If you are not on version 1.1.4, upgrade the plugin to version 1.1.4.
After upgrading, test your site’s WordPress pages related to the plugin and confirm the plugin version in the WordPress Plugins screen remains 1.1.4.
If you cannot upgrade immediately, disable the wp2android-turn-wp-site-into-android-app plugin until you can update.

Usually a quick update

Check it yourselfA free Nuclei check exists for this CVE. Run it against your hosts.Is your organisation exposed?Discuss checks for your systems with a specialist. Scope is agreed before testing.

What it is

From the CVE record

Vulnerability in wordpress plugin wp2android-turn-wp-site-into-android-app v1.1.4, The plugin includes unlicensed vulnerable CMS software from http://www.invedion.com.

In plain language

Written by AI from the record

A vulnerability in the WordPress plugin wp2android-turn-wp-site-into-android-app (v1.1.4) could let an attacker compromise your site if they can reach your WordPress site; most small businesses should take action by updating the plugin.

wp2android-turn-wp-site-into-android-app contains a vulnerability (CWE-434) that can be abused through the WordPress site to compromise the hosting environment; a public exploit exists, and there is a published fix with the plugin being fixed in version 1.1.4.

If you're affected

Full website compromise
Customer/admin data exposure
Site defacement or downtime
Malware or backdoor planting

What is it

This is a weakness in a WordPress plugin that can allow an attacker to take control of your website. Think of it like a door in a storefront that’s built with a broken lock: if someone finds it, they may get in and cause damage.

Who is affected

This matters if you use the WordPress plugin “wp2android-turn-wp-site-into-android-app” on your business website. Because a public exploit exists, attackers may try it against exposed WordPress sites.

It is primarily a risk when the plugin is installed and reachable through your WordPress website (for example, via normal website access to your WordPress site).

How urgent is it

This is an AMBER issue because there is a public exploit available, and security attention around it is rising. While there’s no confirmation it’s on the official “known exploited” list, the existence of a working exploit means you should act now rather than later.

Update or disable the plugin as soon as you can to reduce the chance of an attacker leveraging it.

What to do — in detail

Confirm whether you’re exposed

Log into your WordPress admin dashboard.
Go to Plugins and locate wp2android-turn-wp-site-into-android-app.
Note the installed version (look specifically for whether it is older than or otherwise not aligned with the fixed version).

Apply the fix

Upgrade wp2android-turn-wp-site-into-android-app to 1.1.4 (this is the fixed version indicated).
After upgrading, refresh the plugin details page (or the Plugins list) to confirm the version is now 1.1.4.
Re-test key site pages and any plugin-related features to ensure everything still works.

If you can’t upgrade right away

Temporarily disable the wp2android-turn-wp-site-into-android-app plugin.
Keep the plugin disabled until you complete the upgrade to 1.1.4.

What to watch for after changes

Unusual admin user creation or permission changes.
Unexpected new files in the WordPress directory (especially if your host provides file-change alerts).
Unexpected redirects, new scripts, or sudden changes to page content.

Exploitation tracking

This CVE is not listed in the CISA KEV catalog based on the provided findings, so treat it as “actively plausible” because a public exploit exists, not “definitely widespread.”

Technical context

CVE-2017-1002003 affects the WordPress plugin wp2android-turn-wp-site-into-android-app. The weakness is categorized as CWE-434. The provided findings indicate a public exploit is available and that the plugin has a fix available with the plugin being fixed in version 1.1.4.

Verdict context: There is no KEV listing in the findings, so exploitation-at-scale is not confirmed by CISA KEV here. A press-attention signal is rising, and exploitation likelihood is predicted (EPSS), but public blocks should not rely on prediction—act because a working public exploit exists.

What “CWE-434” means in practice for defenders: it points to an input/file-handling weakness where an attacker may be able to upload or cause unsafe handling of content that should not be allowed, enabling compromise depending on how the plugin uses the bundled/embedded components.

This is a general assessment based on public vulnerability data. It does not account for your specific infrastructure — when in doubt, consult a security specialist.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS96th

Public exploit

CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

1 source with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in

EPSS

12% chance of exploitation activity in the next 30 days, which ranks it in the 96th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

23 events over 3296 days, from the signal feeds we watch.

2026-09-23EPSS band changelow → moderateepss band change
2026-09-21EPSS band changemoderate → lowepss band change
2026-09-06EPSS band change0 → moderateepss band change
2026-09-05EPSS band changemoderate → 0epss band change
2026-08-31EPSS band change0 → moderateepss band change
2026-08-29EPSS band changemoderate → low

Affected products

invedioncommercial
- wp2android-turn-wp-site-into-android-appOn-premWeb & CMS Plugins / wordpress-plugin
wp2android-turn-wp-site-into-android-app projectoss-project
- wp2android-turn-wp-site-into-android-appOn-premWeb & CMS Plugins / wordpress-plugin

Technical detail

CVSS 3.0 vector

Open in the CVSS calculator

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

Scored 9.8 by NVD.

How it is reached

Attack Vector NetworkExploitable remotely over the network without any special conditions
Attack Complexity LowNo special conditions — the attack can be reliably reproduced
Privileges Required NoneNo authentication required — anyone can exploit this
User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

Confidentiality HighTotal information disclosure — all data in the component is compromised
Integrity HighTotal loss of integrity — attacker can modify any data in the component
Availability HighTotal denial of service — the component is completely unavailable