WPZOOM Portfolio < 1.4.34 - Contributor+ Arbitrary Post/Page Type Overwrite via IDOR
CVSS score
—
EPSS probability
—
Risk score
—
Published
4 h ago
Resmî kaynaklarda yeterli kanıt bulunamadı. Bu sonuç “yama yok” anlamına gelmez.
Impact on My Inventory
Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.
Checking session…
Vulnerability description
DayBreach AI Explanation
Verified against sourcesSources read
2
Source agreement
Tam uyum
Evidence confidence
%61
Short explanation
In WPZOOM Portfolio Lite versions prior to 1.4.34, users with the contributor role or higher can exploit an IDOR flaw to convert other users' posts or pages into portfolio items, removing them from original listings and URLs. (S0, S1, S2)
Unauthorized content alteration and loss of access compromise site integrity and user trust.
What should be done?
- Restrict contributor and higher privileges to only necessary actions (S0).
- Update the plugin to the latest version; if none is available, monitor the vendor advisory (S0).
- Deploy security plugins or a WAF that enforce proper capability checks (S0).
- Monitor logs for unexpected post‑type changes (S0).
- Remove the plugin if it is not required (S0).
The sources give limited detail on some technical conditions. Review the chain of evidence below before deciding how to act.
Chain of evidence and sources
WPZOOM Portfolio Lite < 1.4.34 sürümünde contributor ve üzeri rolündeki kullanıcılar, IDOR üzerinden başka kullanıcıların gönderi tipini değiştirebilir (S0, S1, S2).
Bu zafiyet için CISA KEV listesinde aktif istismar kaydı bulunmamaktadır (S0).
Resmî kaynaklarda yama durumu doğrulanamadı; yama yok anlamına gelmez (S0).
Show the technical text from the sources
The WPZOOM Portfolio Lite WordPress plugin before 1.4.34 does not check that a user is allowed to edit a post before changing its type and order, which could allow users with the contributor role and above to convert any other user's posts and pages into portfolio items, removing them from their original listings and URLs.
This explanation was compiled automatically from the source records. Scores, active exploitation, patch and exploit status come straight from the sources.
IMPACT: Affected Products and Software
Affected Products
The following products are affected by CVE-2026-110514 vulnerability. Where our threat engine knows the exact affected versions, they are listed below.
| ID | VENDOR | PRODUCT | ACTION |
|---|---|---|---|
| 1 | Unknown | WPZOOM Portfolio Lite | View |
RED HAT CSAF/VEX: Product Impact Check
SCORING: CVSS from Multiple Sources
CVSS Scores
The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.
| SCORE | VERSION | SEVERITY | VECTOR | SOURCE |
|---|---|---|---|---|
| The sources have not yet published a verified CVSS metric. | ||||
Patch and Remediation Guide
Solution & Remediation Advisory
İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.
Public exploit and active exploitation status
Verified exploit intelligence
No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.
Weakness Classification and Attack Patterns (CWE & CAPEC)
CWE - Common Weakness Enumeration
While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-110514 is associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-110514 weaknesses.
Official Sources and Advisories
Yama durumu bilinmiyor
Similar Vulnerabilities
Get this vulnerability through the API
Affected products, version ranges, exploitation status and patch information in a single request, with a free key.
curl -H "x-api-key: $DAYBREACH_API_KEY" \ "https://api.daybreach.dev/api/v1/intel/cves/CVE-2026-110514"