myflash 1.00 and earlier: A security weakness
myflash 1.00 and earlier is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
- Component
- myflash 1.00 and earlier
- Plugin slug
myflash- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- May 03, 2007
- Weakness
- NVD-CWE-Other
This CVE was published May 03, 2007 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update myflash 1.00 and earlier to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
PHP remote file inclusion vulnerability in myflash-button.php in the myflash 1.00 and earlier plugin for WordPress allows remote attackers to execute arbitrary PHP code via a URL in the wpPATH parameter.
NVD vector: AV:N/AC:L/Au:N/C:P/I:P/A:P
Primary and upstream sources
- NVD record for CVE-2007-2485
- Upstream reference alexrabe.boelinger.com
- Upstream reference osvdb.org
- Upstream reference securityfocus.com
- Upstream reference vupen.com
- Upstream reference exchange.xforce.ibmcloud.com
- Upstream reference exploit-db.com
- Upstream reference alexrabe.boelinger.com
- Upstream reference osvdb.org
- Upstream reference securityfocus.com
- Upstream reference vupen.com
- Upstream reference exchange.xforce.ibmcloud.com
- Upstream reference exploit-db.com