SQL Injection
2 records50%First: 2015. Latest: 2015.
Plugin security history
The Wordfence Intelligence dataset currently contains 4 vulnerability records associated with Awesome Filterable Portfolio, published between 2015 and 2022.
Dataset last synchronized: 2026-08-02 09:41:47 UTC
At a glance
| Year | Records | Relative volume |
|---|---|---|
| 2015 | 2 | |
| 2022 | 2 |
| Severity | Records | Share |
|---|---|---|
| High | 4 | 100% |
First: 2015. Latest: 2015.
First: 2022. Latest: 2022.
First: 2022. Latest: 2022.
Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.
1.9Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.
| Affected range | Vulnerability | Published | Patched version | Severity |
|---|---|---|---|---|
*-1.9.7 | Awesome Filterable Portfolio <= 1.9.7 - Unauthenticated Stored Cross-Site Scripting | September 15, 2022 | Not supplied | High |
*-1.9.7 | Awesome Filterable Portfolio <= 1.9.7 - Missing Authorization to Plugin Settings Change | September 15, 2022 | Not supplied | High |
[*, 1.9) | Awesome Filterable Portfolio < 1.9 - Blind SQL Injection | July 7, 2015 | 1.9 | High |
[*, 1.9) | Awesome Filterable Portfolio < 1.9 - Blind SQL Injection | July 7, 2015 | 1.9 | High |
Selected source records
Published: September 15, 2022
Published: September 15, 2022
Published: July 7, 2015
Published: July 7, 2015
Published: September 15, 2022
Published: July 7, 2015
Published: September 15, 2022
Published: July 7, 2015
Published: September 15, 2022
Published: September 15, 2022
Running an affected version does not prove that a website was compromised. Suspicious redirects, unknown administrators, injected content, unexpected files or recurring malware may require a manual investigation.
Vulnerability data: Wordfence Intelligence. Analysis and practical guidance: 3Zero Digital.
This page aggregates active Production Feed records. Counts are not software-quality rankings, and an affected version does not prove exploitation or infection. Read the full methodology.