Appthemes Classipress up to 3.1.5 facebook_id cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Appthemes Classipress 3.0.5.2/3.0.5.3/3.1.3/3.1.4/3.1.5. Impacted is an unknown function. This manipulation of the argument facebook_id causes cross site scripting. This vulnerability is handled as CVE-2011-5257. The attack can be initiated remotely. Additionally, an exploit exists. You should upgrade the affected component.
Details
A vulnerability classified as problematic was found in Appthemes Classipress 3.0.5.2/3.0.5.3/3.1.3/3.1.4/3.1.5. Affected by this vulnerability is some unknown functionality. The manipulation of the argument facebook_id with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity. The summary by CVE is:
Multiple cross-site scripting (XSS) vulnerabilities in the Classipress theme before 3.1.5 for WordPress allow remote attackers to inject arbitrary web script or HTML via the (1) twitter_id parameter related to the Twitter widget and (2) facebook_id parameter related to the Facebook widget.
The weakness was released 02/12/2013 (Website). The advisory is shared at exploit-db.com. This vulnerability is known as CVE-2011-5257 since 02/12/2013. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept.
Upgrading to version 3.1.4 eliminates this vulnerability.
The vulnerability is also documented in the databases at Exploit-DB (18053), OSVDB (76712†) and Secunia (SA46658†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 3.9
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Classipress 3.1.4
Timeline
10/31/2011 🔍02/12/2013 🔍
02/12/2013 🔍
02/12/2013 🔍
03/24/2015 🔍
02/02/2025 🔍
Sources
Advisory: exploit-db.comStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2011-5257 (🔍)
GCVE (CVE): GCVE-0-2011-5257
GCVE (VulDB): GCVE-100-63541
Secunia: 46658 - WordPress ClassiPress Theme "twitter_id" and "facebook_id" Script Inse, Less Critical
OSVDB: 76712
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/24/2015 12:22Updated: 02/02/2025 23:37
Changes: 03/24/2015 12:22 (54), 02/25/2019 09:38 (4), 02/02/2025 23:37 (18)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.