LiveActive security incident?Get immediate response
CVE Record

CVE-2023-3344: Auto Location for WP Job Manager via Google < 1.1 - Admin+ Cross Site Scripting

The Auto Location for WP Job Manager via Google WordPress plugin before 1.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)

MediumCVSS 4.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a stored cross-site scripting issue in a WordPress plugin. An administrator-level user could save unsafe script content in plugin settings, even where WordPress normally blocks unfiltered HTML, such as multisite environments. The business risk is limited by the high privilege requirement, but compromised or misused admin accounts could affect visitors or other users.

Executive priority

Treat as a medium-priority remediation item. It is not remotely exploitable by unauthenticated users based on the provided sources, but it can weaken WordPress security boundaries if an admin account is compromised or misused.

Technical view

Auto Location for WP Job Manager via Google before 1.1 fails to sanitize and escape some settings. The issue is CWE-79 stored XSS with CVSS 3.1 score 4.8. Attack prerequisites are high privileges and user interaction, with changed scope and low confidentiality and integrity impact.

Likely exposure

Exposure is likely limited to WordPress sites running Auto Location for WP Job Manager via Google before 1.1. Multisite deployments are specifically relevant because the issue bypasses the protection expected when unfiltered_html is disallowed.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. WPScan is listed as a technical reference with an exploit tag, but no provided source establishes exploitation in the wild.

Researcher notes

The key constraints are PR:H and UI:R. The provided data identifies stored XSS in settings handling, not a broader unauthenticated attack path. Do not assume affected CPEs or active exploitation beyond the supplied WPScan and CVE metadata.

Mitigation direction

  • Upgrade the plugin to version 1.1 or later if still in use.
  • Remove the plugin if it is unnecessary or unsupported.
  • Restrict administrator access to trusted accounts only.
  • Review plugin settings for unexpected script or markup changes.
  • Check vendor and WPScan guidance for any additional remediation details.

Validation and detection

  • Inventory WordPress sites for the affected plugin and version.
  • Confirm whether any installation is below version 1.1.
  • Identify multisite deployments where unfiltered_html is disabled.
  • Review administrator account activity around plugin settings changes.
  • Verify that updated sites no longer run the vulnerable version.
Prepared
Confidence
high
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-79: 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-3344 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.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/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.8CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N1.72.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
UnknownAuto Location for WP Job Manager via Google0unaffected
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.