Security readout for executives and security teams
Plain-English summary
A vulnerable uListing plugin could let an unauthenticated attacker tamper with database queries through a public-facing WordPress site. The main business risk is unauthorized database manipulation and limited data exposure or disruption for sites running uListing <= 2.0.3. The provided sources do not show confirmed active exploitation.
Executive priority
High priority for any public WordPress site using uListing. The issue is unauthenticated, network reachable, and can affect database integrity. Urgency depends on whether the plugin is installed and exposed.
Technical view
CVE-2021-36880 is an unauthenticated SQL injection in StylemixThemes uListing for WordPress, versions <= 2.0.3, involving the custom parameter. CVSS 3.1 score is 8.6: network reachable, low complexity, no privileges, no user interaction, with high integrity impact and lower confidentiality and availability impact.
Likely exposure
Exposure is limited to WordPress sites with the uListing plugin installed at version 2.0.3 or earlier. Internet-facing sites have the highest concern because the vulnerability requires no authentication.
Exploitation context
The vulnerability is remotely reachable and low complexity, but the bundle marks KEV as false and provides no cited evidence of active exploitation. Treat exploit availability and real-world targeting as unconfirmed from these sources.
Researcher notes
Analysis is constrained to the supplied CVE, CVSS, Patchstack, and WordPress.org references. The bundle identifies the vulnerable parameter as custom but does not provide safe reproduction detail, observed exploitation, or a specific fixed version.
Mitigation direction
- Inventory WordPress sites for uListing plugin installations and versions.
- Prioritize remediation for internet-facing sites running uListing <= 2.0.3.
- Check StylemixThemes, WordPress.org, and Patchstack guidance for fixed versions or vendor mitigations.
- Disable or remove the plugin where business use is not required.
- Back up and review affected site databases before major remediation work.
Validation and detection
- Confirm plugin version from WordPress admin or asset inventory.
- Verify whether any public site still runs uListing <= 2.0.3.
- Review web and application logs for suspicious unauthenticated requests involving uListing functionality.
- Check database integrity for unexpected listing, user, or configuration changes.
- Document remediation status for every identified WordPress instance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-36880 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L3.94.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.6HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://wordpress.org/plugins/ulisting/#developersCVE reference · x_refsource_CONFIRM
- https://patchstack.com/database/vulnerability/ulisting/wordpress-ulisting-plugin-2-0-3-unauthenticated-sql-injection-sqli-vulnerabilityCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.