LiveActive security incident?Get immediate response
CVE Record

CVE-2023-35044: WordPress Securimage-WP Plugin <= 3.6.16 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Drew Phillips Securimage-WP plugin <= 3.6.16 versions.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE affects the WordPress Securimage-WP plugin through version 3.6.16. It is a CSRF issue, meaning an attacker may be able to trick a logged-in user into causing an unintended change. The published severity is medium, with low integrity impact and no stated confidentiality or availability impact.

Executive priority

Treat this as a moderate-priority WordPress plugin risk. It is not reported as actively exploited in the provided sources, but exposed sites should be inventoried and remediated because CSRF can create unauthorized changes through user interaction.

Technical view

CVE-2023-35044 is classified as CWE-352 in Drew Phillips Securimage-WP for WordPress <= 3.6.16. The CVSS 3.1 score is 4.3: network attack vector, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact, and no confidentiality or availability impact.

Likely exposure

Exposure is limited to WordPress sites that have the Securimage-WP plugin installed at version 3.6.16 or earlier. The source bundle does not identify affected CPEs or a broader product family.

Exploitation context

The CVSS vector indicates exploitation requires user interaction but no attacker privileges. The source bundle does not show CISA KEV listing or any cited evidence of active exploitation, so active exploitation should not be assumed.

Researcher notes

Evidence is sparse beyond the CVE metadata and Patchstack vulnerability entry. Do not infer a specific affected action, endpoint, nonce failure, patch version, or exploitability beyond the stated CSRF classification and CVSS vector.

Mitigation direction

  • Inventory WordPress sites for Securimage-WP plugin version 3.6.16 or earlier.
  • Check Patchstack and vendor guidance for a fixed version or replacement advice.
  • Disable or remove the plugin where it is not required.
  • Restrict administrative sessions and avoid unnecessary privileged browsing.
  • Monitor WordPress change logs for unexpected settings or content changes.

Validation and detection

  • Confirm whether Securimage-WP is installed on each WordPress instance.
  • Record the installed plugin version and compare it with <= 3.6.16.
  • Review vendor or Patchstack advisories for current remediation status.
  • Check whether unexpected administrative changes occurred around relevant user sessions.
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 · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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
cve · low confidence lookup

CVE-2023-35044 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
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/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
Drew PhillipsSecurimage-WPsecurimage-wp, n/aunaffected
Weakness

CWE details

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.