Amministrazione Aperta <= 3.7.3 - Admin+ Local File Inclusion
Strategic Overview
- Status
- Patched in 3.8
- Affected Plugin
- Amministrazione Aperta
- Affected Version
<= 3.7.3- CVSS
- 5.4Medium
- Weakness type
- CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
- CVE
CVE-2022-1560
At a glance
CVE-2022-1560 is a medium-severity Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in the Amministrazione Aperta WordPress plugin, affecting versions <= 3.7.3. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.8; sites on affected versions should update now. Disclosed March 2022, reported by Hassan Khan Yusufzai - Splint3r7.
Vulnerability Overview
The Amministrazione Aperta WordPress plugin through 3.7.3 does not validate the open parameter before using it in an include statement, leading to a Local File Inclusion issue. The original advisory mentions that unauthenticated users can exploit this, however the affected file generates a fatal error when accessed directly and the affected code is not reached. The issue can be exploited via the dashboard when logged in as an admin, or by making a logged in admin open a malicious link. CVE-2022-50956 is a duplicate of this.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
Reaching this weakness in Amministrazione Aperta <= 3.7.3 takes a caller who can reach the endpoint. PHP file inclusion means a path used by include or require is built from request data, so the file that gets executed is under the caller's influence.
Including an attacker-influenced file executes its contents, which is why this class is routinely chained with an upload or log-poisoning step to reach code execution. For Amministrazione Aperta the fix is 3.8: builds <= 3.7.3 are affected, anything from 3.8 onward is not.
Remediation
Update to version 3.8, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Amministrazione Aperta: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Amministrazione Aperta 3.8 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C