LiveActive security incident?Get immediate response
CVE Record

CVE-2012-5873: ARC (aka ARC2) through 2011-12-01 allows reflected XSS via the end_point.php query parameter in an output=h...

ARC (aka ARC2) through 2011-12-01 allows reflected XSS via the end_point.php query parameter in an output=htmltab action.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a reflected cross-site scripting issue in legacy ARC/ARC2. If an exposed endpoint is vulnerable, attacker-supplied input can be reflected into a web response, potentially affecting users who access that endpoint. The source bundle does not show active exploitation or confirmed vendor remediation details.

Executive priority

Treat this as a moderate legacy-web risk. It should not displace actively exploited critical vulnerabilities, but exposed obsolete ARC/ARC2 deployments should be identified and remediated because XSS can undermine user trust and application integrity.

Technical view

CVE-2012-5873 is CWE-79 in ARC, also known as ARC2, through 2011-12-01. The described issue is reflected XSS via the end_point.php query parameter during an output=htmltab action. CVSS v3.1 is 5.3 medium, with network attack vector and low complexity.

Likely exposure

Exposure is most likely in legacy ARC/ARC2 installations from 2011-12-01 or earlier where end_point.php is reachable. The structured affected-product data is incomplete, listing vendor and product as n/a, so asset confirmation requires local inventory review.

Exploitation context

The CVE is not listed as CISA KEV in the source bundle. No cited source confirms exploitation in the wild. The public description identifies a reflected XSS condition, but the bundle does not provide validated exploit status, fixed versions, or operational impact beyond integrity risk.

Researcher notes

The record is sparse: affected CPEs are absent, vendor/product are n/a, and only one advisory reference is supplied. Avoid broad product claims. Focus validation on confirmed ARC/ARC2 code lineage, endpoint reachability, and whether maintained guidance exists.

Mitigation direction

  • Inventory any ARC or ARC2 deployments and identify versions at or before 2011-12-01.
  • Check ARC/ARC2 vendor or project guidance for fixed versions or official remediation.
  • Restrict public access to end_point.php where the endpoint is not business-required.
  • Review input handling and output encoding around the affected query parameter.
  • Prioritize replacement if the deployed ARC/ARC2 code is unmaintained.

Validation and detection

  • Confirm whether ARC or ARC2 exists in application dependency and server inventories.
  • Check whether end_point.php is deployed and externally reachable.
  • Review application routing for output=htmltab use on the affected endpoint.
  • Use approved XSS testing safely in a non-production or authorized environment.
  • Document whether compensating access controls limit exposure.
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-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-2012-5873 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/AC:L/AV:N/A:N/C:N/I:L/PR:N/S:U/UI: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/AC:L/AV:N/A:N/C:N/I:L/PR:N/S:U/UI:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AC:L/AV:N/A:N/C:N/I:L/PR:N/S:U/UI: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
n/an/an/aListed
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.