CVE-2023-6962
Joomunited Wp Meta Seo ≤ 4.5.13
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-6962 is a medium-severity Exposure of Sensitive Information Through Metadata (CWE-1230) vulnerability in Joomunited Wp Meta Seo. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-59158
Vulnerability Data
The WP Meta SEO plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.5.12 via the meta description. This makes it possible for unauthenticated attackers to disclose potentially sensitive information via the meta…
more
description of password-protected posts.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.4.2V12.1.5V13.3.2V14.2.8
Mitigating Controls (NIST 800-53 r5) AI
Enforces approved authorizations for logical access to stored information, directly stopping unauthorized read/write.
Requires protection of confidentiality/integrity for information at rest, directly addressing insecure storage.
Information flow enforcement can be configured to treat metadata as protected information and block its unauthorized release.
Limits privileges so only authorized accesses to sensitive stored data are permitted.
Associating and enforcing security/privacy attributes on objects directly governs what metadata may be exposed.
Requiring security attributes to accompany transmitted data prevents sensitive values from leaking through metadata channels.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Classification helps identify metadata that may need protection, but does not directly limit its exposure.
Labelling can flag sensitive metadata, yet does not enforce technical controls to prevent its disclosure.
Transfer policies can require stripping or protecting metadata, but coverage is indirect.
Access-control rules can be extended to metadata objects, though the control is not metadata-specific.
Data-masking techniques can obscure sensitive metadata values, providing partial mitigation.
DLP solutions can detect and block metadata leakage, yet are not designed solely for this weakness.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-922, a class-level weakness. Rules are authored against its narrower children: CWE-312.