Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V3 - Web Frontend Security Anti-CSRF tokens, SameSite cookies
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 23, 2026
Cross-Site Request Forgery in the ApusListing WordPress theme (versions 1.2.63 and earlier) lets a remote, unauthenticated attacker forge privileged state-changing requests that a logged-in victim's browser executes, chaining into a broken-authentication condition that can lead to account or session compromise. Reported by Patchstack and rated CVSS 8.8, exploitation requires tricking an authenticated user into visiting attacker-controlled content (UI:R). There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Know when Apuslisting gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Primary rating from Vendor (Patchstack) · only source for this CVE.
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Cross Site Request Forgery (CSRF) in ApusListing <= 1.2.63 versions.
Executive ViewAI
ApusListing WordPress theme versions 1.2.63 and earlier contain a critical CSRF vulnerability that enables unauthenticated attackers to hijack authenticated user sessions and compromise accounts. Organizations deploying this theme face direct exposure to account takeover, unauthorized administrative actions, and potential data compromise without immediate remediation.
Within 24 hours, inventory all WordPress installations using ApusListing versions 1.2.63 or earlier; restrict administrative access and disable the theme if not actively required in production. Over the next 7 days, deploy Web Application Firewall rules to block CSRF attack patterns, review authentication and access logs for exploitation indicators, and enforce anti-CSRF tokens and SameSite cookie policies on affected systems. Within 30 days, monitor Patchstack and WordPress.org for vendor patches; establish expedited deployment procedures for immediate application upon release, or evaluate and migrate to alternative maintained themes if no patch becomes available.
Enforce CSRF token validation and SameSite cookie policies (Strict mode preferred); deploy WAF rules filtering cross-origin state-changing requests to administrative functions; implement Content Security Policy headers to restrict unauthorized script execution; require step-up authentication (re-login) for sensitive account or administrative actions; disable or isolate the theme from production where operationally feasible; monitor authentication logs and access patterns for indicators of account compromise or session hijacking.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.
EUVD-2026-48182
GHSA-2qrw-v6m9-cjjq
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB