CVE-2026-14183 Classified Listing vulnerability
The Classified Listing WordPress plugin before 5.3.9 does not verify that the order targeted by its payment-receipt handler belongs to the requesting user, allowing authenticated users with subscriber-level access to read the payment receipt details of any other user's order.
Browse WordPress security risksQuick answer
RadiusTheme Classified Listing should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- < 5.3.9
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-14183 affects Classified Listing and involves security-control failure. Successful exploitation may affect the confidentiality, integrity, or availability of the affected workflow. Prioritize deployments that process untrusted input, expose the affected feature, or hold sensitive data. Upgrade the Classified Listing WordPress plugin to 5.3.9 or later.
- Inventory every deployment, device, package, plugin, container, build, and environment that uses Classified Listing.
- Compare the installed version with the recorded affected range: < 5.3.9.
- Upgrade the Classified Listing WordPress plugin to 5.3.9 or later.
- Until patched, disable the affected Classified Listing feature or plugin and restrict its public and administrator endpoints.
- Review configuration, roles, tokens, network paths, and exposed endpoints connected to Classified Listing; remove access that is not required.
- Review application, system, proxy, and audit logs for requests and behavior linked to the affected feature and CVE.
- If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-14183 in place.
- Use a safe regression test to confirm the affected security-control failure path no longer produces the vulnerable behavior.
- Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
- Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
- Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.
Related categories
Related security risks
More published guidance from the same primary category.
CVE-2026-65475 Modula Image Gallery vulnerability
Updated July 24, 2026
highCVE-2026-65500 Manual - Documentation, Knowledge Base & Education WordPress Theme vulnerability
Updated July 24, 2026
highCVE-2026-65511 Manual - Documentation, Knowledge Base & Education WordPress Theme vulnerability
Updated July 24, 2026
Trusted references
FAQ
What is affected by CVE-2026-14183?
RadiusTheme Classified Listing versions listed as affected should be reviewed: < 5.3.9.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.