CVE-2025-68033

Custom Related Posts <= 1.8.0 - Unauthenticated Information Exposure

2025-12-25 00:00

Strategic Overview

Status: Patched in 1.8.1
Affected Plugin: Custom Related Posts
Affected Version: <= 1.8.0
CVSS: 5.3Medium
Weakness type: CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE: CVE-2025-68033

View all Custom Related Posts vulnerabilities

At a glance

CVE-2025-68033 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Custom Related Posts WordPress plugin, affecting versions <= 1.8.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.8.1; sites on affected versions should update now. Disclosed December 2025, reported by MD ISMAIL.

Vulnerability Overview

The Custom Related Posts plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.8.0. This makes it possible for unauthenticated attackers to extract sensitive user or configuration data.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Custom Related Posts <= 1.8.0 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Custom Related Posts the fix is 1.8.1: builds <= 1.8.0 are affected, anything from 1.8.1 onward is not.

Remediation

Update to version 1.8.1, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Custom Related Posts 1.8.1 closes this, and updating the plugin is the step that ends it.

Login Security
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-68033 https://www.wordfence.com/threat-intel/vulnerabilities/id/4df9918b-7201-4cd7-978d-4a1fa207a97c https://nvd.nist.gov/vuln/detail/CVE-2025-68033

Related records

CVSS Vector

5.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityLow
IntegrityNone
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/