LiveActive security incident?Get immediate response
CVE Record

CVE-2023-51667: WordPress Rate my Post – WP Rating System plugin <= 3.4.2 - Broken Access Control vulnerability

Authentication Bypass by Spoofing vulnerability in FeedbackWP Rate my Post – WP Rating System allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Rate my Post – WP Rating System: from n/a through 3.4.2.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-51667 affects the WordPress Rate my Post plugin through version 3.4.2. An unauthenticated attacker may be able to spoof authentication and reach plugin functionality that should be access-controlled. The published impact is limited confidentiality exposure, not data modification or service outage.

Executive priority

Address in normal vulnerability management, with faster handling for public WordPress sites or sites processing sensitive user activity. The score is medium and impact is confidentiality-limited, but unauthenticated network reachability raises operational priority.

Technical view

The issue is a CWE-290 authentication bypass by spoofing in FeedbackWP Rate my Post - WP Rating System, package rate-my-post. CVSS 3.1 is 5.3: network reachable, low complexity, no privileges, no user interaction, unchanged scope, low confidentiality impact only.

Likely exposure

Exposure is likely limited to WordPress sites with Rate my Post - WP Rating System installed at version 3.4.2 or earlier. The source bundle does not identify affected hosting platforms, default configurations, or specific vulnerable endpoints.

Exploitation context

The CVE is not listed as CISA KEV in the provided bundle, and the supplied sources do not state active exploitation. Treat this as internet-reachable WordPress plugin risk, but do not assume confirmed exploitation without additional evidence.

Researcher notes

The public bundle is sparse. It identifies the weakness class, affected plugin and version range, and CVSS vector, but does not provide endpoint detail, proof of concept, exploit telemetry, or a named fixed release. Further validation should stay defensive and source-grounded.

Mitigation direction

  • Inventory WordPress sites for the rate-my-post plugin.
  • Treat Rate my Post versions 3.4.2 and earlier as affected.
  • Check FeedbackWP and Patchstack for official fixed-version or workaround guidance.
  • Prioritize remediation on public, high-traffic, or sensitive WordPress sites.
  • Avoid claiming a specific patch until vendor guidance confirms it.

Validation and detection

  • Confirm installed plugin name, package slug, and version on each WordPress site.
  • Verify no site remains on Rate my Post version 3.4.2 or earlier.
  • Review WordPress access logs for unusual unauthenticated plugin activity.
  • Check security tooling for alerts tied to this CVE or plugin slug.
  • Document sites where the plugin is absent, updated, disabled, or awaiting vendor guidance.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-290: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-51667 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2023-51667Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
FeedbackWPRate my Post – WP Rating Systemrate-my-post, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-290 · source CWE mapping

Authentication Bypass by Spoofing

Authentication Bypass by Spoofing represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.