Unrestricted File Upload in WP-Property plugin for WordPress (CVE-2012-10027)
Summary
Vulnerability in WP-Property plugin for WordPress (CVE-2012-10027). Risk of unauthorized operations or information disclosure. Exploitable via uploadify.php.
Original description
The description as published by the source.
WP-Property plugin for WordPress up to and including version 1.35.0 contains an unauthenticated file upload vulnerability in the third-party uploadify.php script. A remote attacker can upload arbitrary PHP files to a temporary directory without authentication, leading to remote code execution.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2012-10027 has been found in WP-Property plugin for WordPress.
Attackers can target a specific entry point like uploadify.php over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WP-Property plugin for WordPress CVE-2012-10027" on the vendor's site.
CVE-2012-10027 (WP-Property plugin for WordPress) — CWE-434
Attack surface: uploadify.php
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-434) exists in WP-Property plugin for WordPress. Attackers reach the vulnerable code path via uploadify.php.
Check the vendor advisory for the affected versions of WP-Property plugin for WordPress. Attack surface: uploadify.php.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで WP-Property plugin for WordPress を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。